North Star Metric Examples

What makes a metric a "North Star" instead of just a metric?

A North Star Metric is the one number a company chooses to represent the core value its product delivers, selected so that moving it in the right direction requires the product to actually get better for customers, not just busier or more visible. That selection criterion is what separates a real North Star from a vanity metric: a metric can be easy to move and still say nothing meaningful about whether the product is working.

The metric is usually paired with a small set of input metrics, the specific levers a team can pull that feed into the North Star, rather than replaced by a dashboard of everything a team could measure. Treating the North Star as the top of a tree, with input metrics as its branches, is the most common way teams keep the number connected to specific, actionable work rather than treating it as an abstract target no one owns.

What are commonly cited North Star Metric examples, and why were they chosen?

Company	Commonly cited North Star	Why it fits
Airbnb	Nights booked	Every night booked represents a completed exchange between a host and a guest, capturing both sides of the marketplace in a single number tied directly to real value delivered, not just site visits or listings created.
Spotify	Time spent listening	Total time spent listening reflects whether the product is actually delivering on its core promise, ongoing engagement with music, rather than a proxy like app opens or account signups that can rise without real usage growing.
Slack	Messages sent	A team sending messages inside Slack is a team actually using it as its working communication layer, which is a closer proxy for delivered value than seat count or logins alone.

These are widely reported, commonly cited examples circulated across product and growth writing, not primary statements sourced from each company's own investor filings in every case; treat the "why" column as the standard reasoning given for each pick in that secondary reporting, rather than a verbatim quote from the company itself.

Why not just use revenue as the North Star Metric?

Revenue is a lagging output, and it can rise for reasons that have nothing to do with the product delivering more value: a price increase, a one-time enterprise deal, or a seasonal spike can all move revenue while the underlying product experience stays flat or gets worse. A North Star Metric is meant to move early enough, and specifically enough, that a team can act on it before a lagging financial number reflects the problem. That does not mean revenue is unimportant; it means revenue functions better as a business goal the North Star is meant to serve, not as the North Star itself.

How do I pick a North Star Metric for my own product if none of these fit?

Start from the core exchange your product enables, the same way Airbnb's chosen metric ties to a completed booking rather than a page view. Ask what single action, if it happened more often, would mean your product delivered more real value to a user, not just more activity in a dashboard. A B2B collaboration tool might land on something like weekly active teams completing a core workflow, rather than total logins, for the same reason Slack's example above favors messages sent over seat count: the metric has to reflect actual use, not just access.

Once you have a candidate metric, stress-test it against the vanity-metric failure mode directly: could this number go up while a reasonable person using the product would say it got worse? If the answer is yes, the metric needs narrowing, usually by adding a qualifying condition (an active, engaged action) rather than counting a raw total.

Can a North Star Metric change as the product matures?

Yes, and treating it as permanent is itself a common mistake. As a product's core value proposition shifts, through a pivot, a new pricing model, or an expansion into a new use case, the metric that best represents delivered value can shift with it. A company that never revisits its North Star risks optimizing hard for a number that stopped reflecting real value years earlier, which is arguably worse than having no North Star at all, since it creates false confidence.

Who should use this guide, and who should look elsewhere?

This guide fits a product manager building or revisiting a metrics tree for their own product, a founder trying to pick a single north-star-style KPI before their next board update, and a data-curious PM preparing to defend a metric choice in an interview or a strategy review. It is grounded in the same metrics-tree thinking Builders Camp's Data for Product Managers bootcamp teaches: defining a North Star, then breaking it into input metrics and diagnostic KPIs a team can actually act on, rather than a dashboard with no clear owner for each number.

It is not the right fit if you need a single, universal answer for what your company's North Star should be; no external guide can make that call correctly without knowing your specific product, users, and business model. It is also not a source for exact company financial figures; the examples above are commonly cited illustrations of the concept, not verified internal metrics from each company's own reporting.

Once a candidate North Star Metric is chosen, running real customer interviews is the fastest way to check whether it actually tracks value from the user's side, not just from a dashboard, and the RICE prioritization framework is a useful next step for deciding which input metric to invest in first. A defensible North Star is also exactly the kind of evidence a promotion conversation to senior PM or a strategy-round product manager interview expects you to be able to name and defend.