The North Star Metric: Why Most Teams Pick the Wrong One (and How to Find Yours)

I once worked on a product where the entire company was aligned around one metric: monthly active users (MAU). We celebrated when it went up. PMs got promoted when it went up. The board presentation led with it.

Then we noticed something: MAU was growing, but revenue wasn't. Users were signing up, opening the app once, and never coming back. We'd optimised our way into a growth trap - millions of "active users" who weren't experiencing any value.

MAU was a vanity metric masquerading as a North Star Metric. The actual behaviour that predicted retention and revenue was something much more specific - and once we found it, everything changed.

What Is a North Star Metric? A Clear Definition

A North Star Metric (NSM) is a single metric that best captures the core value your product delivers to users, and is predictive of your product's long-term growth and health.

The concept was popularised by Sean Ellis (who coined "growth hacking") and refined by companies like Amplitude. But the underlying principle is older: find the one number that, if it moves in the right direction consistently, means your product is genuinely winning.

The North Star Metric lives at the intersection of two things:

• User value delivered - something users actually experience as valuable
• Business outcome predicted - a leading indicator of revenue, retention, or growth

Real North Star Metric Examples (What Good Looks Like)

Company	North Star Metric	Why It Works
Spotify	Weekly Active Listeners	Measures habit formation, not just sign-ups. Weekly cadence captures retention better than monthly.
Airbnb	Nights Booked	Directly captures the core value exchange. Aligns hosts and guests. Every product decision traces back to it.
Duolingo	Daily Active Users (with streak)	Combines engagement with habit. The streak mechanic is a direct input to this metric, making it highly actionable.
Slack	Messages sent per active org per week	Moves beyond DAU to measure value depth. An org sending more messages is collaborating more, not just logging in.
WhatsApp	Daily Messages Sent	Simple, fundamental, directly measures the product's core utility. Hard to game.
Netflix	% of subscribers who watch >X hours per week	Distinguishes engaged subscribers from "gym membership" subscribers who pay but don't use the product.

Notice the pattern: every strong NSM measures a specific, recurring behaviour that indicates the user got genuine value - not just that they registered or opened the app.

The 4 Criteria Every North Star Metric Must Pass

Run any candidate metric through these four tests. If it fails any one of them, it's not your North Star:

How to Find Your North Star Metric: A Step-by-Step Process

Step 1: Map the "Aha Moment"

Every successful product has an "Aha moment" - the specific moment when a user first experiences the core value. For Facebook in the early days, it was "connecting with 7 friends in 10 days." For Dropbox, it was saving a file in one device and seeing it on another.

What's the behaviour that precedes users staying? Run a cohort analysis: compare users who stayed long-term vs. users who churned in the first 30 days. What did long-term users do in their first week that churned users didn't?

Step 2: Identify the Value Delivery Event

The North Star Metric usually measures or closely correlates with the frequency of value delivery events - the action that represents "the user got what they came for." For a food delivery app, it's a completed order. For a B2B SaaS tool, it might be a project exported or a report shared with a stakeholder outside the platform.

Step 3: Test for Predictive Power

Take your candidate metric and segment users by how often they did that thing in their first 30 days. Do users who did it more have significantly higher 90-day and 180-day retention? If yes, you've found a strong candidate.

Step 4: Check for Actionability

Can you draw a direct line from product decisions to this metric moving? Write down three hypothetical product changes and explain specifically how each one would increase the metric. If you can't, the metric is too abstract.

Step 5: Pressure-Test for Manipulation

Can you game the metric without delivering real user value? If yes, don't use it. "Sessions per user" can be gamed by showing error messages that force refreshes. "Time in app" can be gamed with dark patterns. Your NSM must be hard to move without genuinely improving user value.

"A metric that can be gamed without delivering value is a metric that will be gamed. Choose your North Star Metric with the same care you'd choose the rules of a game - because your team will optimise for whatever you measure."

The North Star Metric Tree: Connecting to Input Metrics

The NSM is not the only metric your team tracks. It's the top of a tree. Below it are input metrics - the specific behaviours and product outcomes that directly drive the North Star. This is where teams get their daily and weekly focus.

Here's an example for a B2B fintech product where the NSM is "Monthly Active Merchants completing at least 3 transactions":

This tree structure means every team has a clear metric they own that connects directly to the North Star. Nobody is working on something disconnected from the core outcome.

Common North Star Metric Mistakes (And How to Fix Them)

Mistake 1: Choosing a Business Metric

Revenue, ARR, GMV - these are outcomes of delivering user value, not measures of it. When you optimise for revenue directly, you end up with perverse incentives: dark patterns, cancellation friction, artificial upsells. Teams feel the tension between "doing what's right for users" and "hitting the number." This tension disappears when your NSM measures user value.

Mistake 2: Choosing a Vanity Metric

App installs, registrations, page views, total users. These are easy to move (just buy more ads) but don't predict retention or revenue. A product with 10 million registered users and a 2% 30-day retention rate is failing. The vanity metric hides the failure.

Mistake 3: Picking a Metric Nobody Understands

"Engagement score" based on a weighted formula of 12 different actions. Sounds sophisticated. In practice, nobody on the team can tell you on any given day whether the metric is going up or down, or which product decision moved it. If your NSM requires a data analyst to explain it, it's too complex.

Mistake 4: Changing the NSM Every Quarter

The North Star Metric should be stable across years, not quarters. If you change it every planning cycle, teams never build the deep intuition about what actually drives it. The NSM should only change when your core business model changes.

Mistake 5: Having Multiple "North Stars"

"We have three North Star Metrics." This is like saying "we're going north-northwest." When resources are constrained and you need to make a hard call, multiple North Stars force you to make trade-offs with no clear prioritisation principle. Pick one. Track others as supporting metrics, not as equals.

Aligning Your Team Around the North Star Metric

Finding the right NSM is half the work. Getting your organisation to actually use it is the other half. Here's what works:

Make It Visible Every Day

The NSM should be on the main dashboard that opens when anyone in the product and engineering team sits down. Not buried in a BI tool. Not in a weekly report. The default view when you open your analytics tool should be: "Here's where our North Star Metric is right now."

Require NSM Traceability in Every PRD

Every Product Requirements Document should answer: "How does this feature move the NSM?" If a PM can't answer that question, the feature probably shouldn't be prioritised. This one change will eliminate 30% of your roadmap backlog - features that exist because someone internally wanted them, not because they drive core user value.

Review the NSM Tree in Sprint Planning

Start every sprint planning with: "What is the NSM this sprint? Which input metric are we targeting?" This connects day-to-day engineering work to the strategic outcome. Engineers who understand why they're building something build it better.

Celebrate Input Metric Wins, Not Just NSM Wins

The NSM moves slowly. If you only celebrate NSM movement, teams feel disconnected from outcomes week-to-week. Celebrate when an input metric meaningfully improves - it's evidence that you're doing the right things.