How to Define Your Product's North Star Metric (With Real Examples from Spotify, Slack, and Netflix)

"What's your north star metric?" might be the most-asked question in product strategy. And yet most teams answer it wrong—picking a metric their CEO likes, choosing something that sounds strategic but cannot be influenced by their team, or conflating the NSM with revenue (which is almost always the wrong call).

Here is a practical framework for getting it right, grounded in how companies that actually did it well made their decisions.

What a North Star Metric Actually Is (And What It Isn't)

A North Star Metric (NSM) is the single measurable number that best captures the core value your product delivers to customers—and is directly tied to long-term sustainable growth.

That definition has two critical components that teams regularly violate:

Core value to customers, not to your CFO. Revenue is a lagging output. An NSM should measure whether customers are getting the thing they came for.

Long-term sustainable growth, not a short-term engagement hack. Watch time can be a great NSM (Netflix) or a terrible one (an app optimizing for outrage). The difference lies in what behavior you are incentivizing.

What an NSM is not: a KPI dashboard metric, a business objective, or a leading indicator of something your investors care about this quarter. It is the single number that, if you move it in the right direction, you can be confident the business is healthy and delivering real value.

The Four-Step Framework for Choosing Your NSM

Step 1: Start with the Aha Moment

Before you can pick a metric, identify the exact moment when a user first experiences the core value of your product. This is different for every product:

For Slack, it was when a team sent its first 2,000 messages. After that threshold, 93% of teams stayed.
For Airbnb, it was the first successful booking on both sides of the marketplace.
For Spotify, it was the moment users realized they could find any song they wanted, immediately.

Map your user journey, identify when the "this is actually useful" realization happens, then ask: what action or behavior best predicts that this moment will repeat?

Step 2: Apply the Value Capture Test

A good NSM passes three tests simultaneously:

Value test: Does this metric increase when users get more value from the product? If it goes up when users are happy and down when they are frustrated, it is a good proxy.

Influence test: Can your product team directly move this metric through product decisions? If only the sales team or macroeconomic conditions can move it, it is not a product NSM.

Sustainability test: Can this metric grow for 5+ years without being gamed or hitting a natural ceiling? Session count can be gamed. Genuine value delivery cannot.

Revenue fails the influence and sustainability tests. Page views fail the value test. This is why most metrics that companies default to are actually poor NSMs.

Step 3: Study Real-World Examples

Netflix → Watch Hours Watch time captures value delivery (users watching = users getting entertainment), is directly influenced by product quality (better recommendations = more watching), and scales indefinitely. The risk: optimizing for watch time without quality filtering led Netflix to invest in content that drove engagement but not retention. Lesson: your NSM can have a dark side. Always pair it with a counter-metric (satisfaction scores, cancellation rate).

Slack → Messages Sent Between Teams Not just messages—messages between teams. This specificity is intentional. A team that only messages internally has not yet experienced Slack's core value: breaking down organizational silos. The NSM captures quality of usage, not just quantity.

Spotify → Time Spent Listening As a music platform, time listening directly measures whether Spotify is delivering on its core promise. This NSM transcended the product format—when podcasts grew, the same metric applied.

Airbnb → Nights Booked A classic two-sided marketplace NSM. It captures value for hosts (revenue) and guests (experiences), and it only goes up if the core product works—matching the right guest with the right host at the right time.

Step 4: Define Your Input Metrics

Once you have your NSM, you need 3-5 input metrics—lever metrics that your team can directly control and that most directly move the NSM. For a consumer app with "Weekly Active Users" as its NSM, input metrics might be:

Acquisition: New accounts created this week
Activation: % of new accounts completing the onboarding flow
Retention: D7 retention rate of cohorts
Resurrection: % of churned users reactivated in the past 30 days
Engagement: Median number of core actions per session

Each input metric should have a clear owner and a specific experiment roadmap connected to it. If you cannot connect an input metric to at least three concrete product experiments, it is too abstract to be useful.

The Most Common NSM Mistakes (And How to Avoid Them)

Mistake 1: Picking revenue as your NSM Revenue is an output, not a value indicator. A PM who moves revenue by making it harder to cancel subscriptions has not improved the product. Use revenue as a business health check, not as your product NSM.

Mistake 2: Choosing an NSM that your team cannot influence If only the marketing team or the sales team can move your NSM, it is not a product metric. Product teams need something they can run experiments against and see results within 2-4 weeks.

Mistake 3: Gaming via perverse incentives Meta famously optimized for engagement and found that outrage-generating content was the most "engaging." Their NSM was technically moving in the right direction while the product became actively harmful. Always pair your NSM with a counter-metric that captures what you do not want to optimize for.

Mistake 4: Never revisiting it Your NSM should be stable enough to anchor a multi-quarter strategy, but not so sacred that it cannot evolve. When Airbnb expanded from accommodation to experiences, their NSM evolved too. Schedule an annual review.

Aligning Your Team Around the NSM

An NSM only works if the entire product org can articulate it and draw a direct line from their daily work to moving it. Three things that make the difference:

Display it everywhere. In the weekly product standup, on the team dashboard, in the OKR doc. If people have to look it up, it is not internalized.

Trace every roadmap item back to it. For every feature in your roadmap, answer: "Which input metric does this move, and by how much?" If you cannot answer this, the feature does not belong on the roadmap.

Celebrate input metric movement, not just NSM movement. Your NSM moves slowly. Input metrics move faster. Teams that only celebrate NSM wins lose motivation on long time horizons.

Sharp metric instincts separate PMs who get promoted from those who stay stuck. Practice defining north star metrics for real products with PM Streak's daily challenge—each prompt is designed to build exactly this kind of rigorous thinking. Sign up and start your streak today.