What is North star metric?
By Heemang Parmar · Updated July 2026 · Editorial policy
A north star metric is the single measurement that best captures the core value a product delivers to its users, chosen so that sustained growth in that one number reflects genuine business progress rather than vanity activity.
Spotify's north star is time spent listening; Airbnb's is nights booked; a B2B tool's might be weekly active teams. The point of naming one number is decision speed: roadmap debates get settled by asking which option moves it most, and every function can trace its work to the same target. The name comes from celestial navigation: one fixed point that every decision can orient against.
A good north star has three properties: it reflects user value (not just revenue), it is a leading indicator (it moves before churn or growth do), and every team can influence it. "Signups" usually fails the first test, since people can sign up and get nothing, which is why activation and usage metrics tend to win.
The common mistake is picking a vanity metric, or picking five "north stars," which is the same as picking none. One number, reviewed on a cadence, with supporting input metrics beneath it, is the whole discipline. It also belongs in your PRD: every feature should be able to say which needle it is supposed to move.
Why does north star metric matter?
A north star metric matters because alignment is the scarcest resource in a growing company. When marketing optimizes signups, product optimizes engagement, and sales optimizes bookings, every team can hit its targets while the business stalls. One shared metric, Airbnb's nights booked is the classic example, gives every function a common definition of progress and a common language for tradeoffs.
For founders, it also disciplines the roadmap. Features that cannot explain their effect on the metric are usually candidates for deferral or deletion, and prioritization frameworks like RICE stay connected to strategy when Impact is scored against the north star rather than against whoever argued loudest. A feature that cannot answer is not automatically dead, but it should have to make an explicit strategic case instead of riding along unexamined.
How does north star metric work?
- 1Define core value: Identify the moment users receive the product's core value; the metric should count that moment, not a proxy.
- 2Test three properties: Confirm it reflects user value, leads revenue and churn rather than trailing them, and every team can influence it.
- 3Add input metrics: Choose three to five supporting drivers, like activation rate or usage frequency, that teams can act on weekly.
- 4Review on a cadence: Track the number weekly, tie roadmap debates to it, and revisit the choice when the strategy meaningfully shifts.
North star metric vs KPI vs OKR: what's the difference?
| Concept | Scope | Timeframe | Example |
|---|---|---|---|
| North star metric | One company-wide measure of delivered value | Years | Nights booked at Airbnb |
| KPI | Many per team or function | Ongoing | Average support response time |
| OKR | Objective plus measurable key results | Quarterly | Grow weekly active teams 20 percent |
How is north star metric used in practice?
Metrics grounded in research
ProductOS starts every project with the Research Agent, which produces multi-source findings with cited sources. Understanding what users actually value is the raw material for choosing a metric that reflects it.
The metric in the PRD
ProductOS's PRD Agent writes the spec section by section across four templates, including Lean. A north star metric gives that document its success measure, so every story can name the needle it moves.
Fast experiment loop
Moving a metric requires shipping experiments quickly. ProductOS projects run in isolated cloud sandboxes with live preview URLs, and the Deploy Agent handles preflight builds, GitHub push, and Vercel deploys, self-fixing up to three times.
Frequently asked questions
What are examples of north star metrics?
Spotify tracks time spent listening, Airbnb tracks nights booked, and Slack famously watched messages sent within teams. The pattern: each counts a moment of delivered value, not a step toward it. Signups and page views fail that test because users can produce both without getting value.
Can a company have more than one north star metric?
Effectively no. The metric's job is to settle tradeoffs, and five tiebreakers cannot break a tie. Most teams pair a single north star with three to five input metrics that individual teams own, which preserves focus while still giving each function a number it can move weekly.
Is revenue a good north star metric?
Usually not, because revenue is a lagging indicator: it moves after value is delivered or lost, too late to steer by. A usage- or activation-based metric leads revenue and is influenceable by every team. Revenue belongs on the dashboard, just not as the north star.
How do I choose a north star metric?
Identify the moment users get the product's core value, then find the number that counts that moment. Test it against three properties: it reflects user value, it leads revenue and churn rather than trailing them, and every team can influence it. Revisit the choice when strategy shifts.
Related terms
- RICE scoringRICE scoring is a prioritization framework that ranks product ideas by multiplying Reach, Impact, and Confidence, then dividing by Effort, producing a single comparable score that shows which backlog items deliver the most value per unit of work.
- BacklogA backlog is the ordered list of features, bug fixes, improvements, and ideas a product team intends to build, ranked so that the items at the top represent the team's actual next commitments rather than a wish list.
- Product requirements document (PRD)A product requirements document (PRD) is a structured specification that defines what a product or feature should do and why, covering the problem, target user, scope, user stories, and acceptance criteria that guide design and engineering.