North Star Metric: The Complete Guide With Examples and a Metric Tree
One number to steer by. What makes a good North Star, how to break it down into a metric tree, and how it goes wrong.
A North Star Metric is the single number that best reflects the value users get from your product and predicts long-term success. A good one reflects value, predicts revenue, is measurable and actionable, and cannot rise for a bad reason. Break it into three to five input metrics owned by teams, and revisit it each quarter.
- What a North Star Metric is
- What makes a good one
- How to choose one
- Breaking it down into a metric tree
- A worked example: how it changes a decision
- North Star vs KPIs vs OKRs
- When a North Star is a bad idea
- Setting targets and a review rhythm
- How it connects to OKRs: a worked link
- Three traps that quietly wreck a North Star
- Common mistakes
Teams drown in metrics. A dashboard with sixty numbers gives everyone a different reason to feel good or bad, and nobody a clear way to decide. The idea behind a North Star Metric is simple and powerful: pick one number that best captures the value your users get, and let the whole team steer by it. This guide explains how to choose one, how to break it down, and how it goes wrong.
What a North Star Metric is
It is the single metric that best reflects the core value your product delivers to users, and which predicts long-term business success. It is not revenue (that is a result, and it lags). It is not vanity (downloads, page views). It is a measure of users successfully getting value.
| Product | Possible North Star | Why it captures value |
|---|---|---|
| Music streaming | Time spent listening to chosen music | Users come to listen; more listening means value delivered |
| Marketplace | Successful transactions per week | Both sides get what they came for |
| Learning app | Lessons completed that lead to improvement | Learning, not just attention |
| Messaging app | Messages sent between active pairs | Real conversations, not signups |
| Accommodation platform | Nights booked | Guests and hosts both succeed |
What makes a good one
The last property is the most important and most ignored. “Time in app” can go up because users love the product, or because they are confused and clicking around. If a number can rise for a bad reason, it will eventually mislead you. I wrote about a real version of this trap in the metric we almost shipped the wrong feature for.
How to choose one
Start with the value: what is the one thing users are trying to achieve with your product? List candidates and test each against the five properties. Pick one and break it down into a few input metrics the team can actually influence. Review it whenever the product or strategy changes materially.
Breaking it down into a metric tree
A North Star alone is too high-level to steer daily work. Split it into the inputs that drive it, so that each team owns something it can move. For an illustrative learning app whose North Star is “weekly learners who complete a lesson and improve”:
This tree turns a company-level number into team-level goals. The growth team owns reach, onboarding owns activation, engagement owns habit, and content owns quality. And because inputs are leading indicators, they move before the North Star does, which is exactly what you need to steer.
A worked example: how it changes a decision
Suppose the team wants to invest in a streak system with animated rewards. Early tests show a clear lift in daily active users and time in app. Looks like a win. But the chosen North Star is “learners who complete lessons and improve”. When the team checks that number, high-streak users are not improving faster than others; they are opening the app to keep the streak alive. The activity is real; the value is not.
With the wrong metric, that feature ships as a success. With the right one, the team sees the gap and shifts effort to the actual bottleneck. That is what a good North Star is for: not to make dashboards prettier, but to make trade-offs easier and to catch vanity wins before they cost a quarter.
North Star vs KPIs vs OKRs
| Concept | What it is | How many |
|---|---|---|
| North Star Metric | The one number that reflects user value | One |
| Input metrics | The levers that drive the North Star | Three to five |
| KPIs | Health measures across the business (revenue, churn, cost) | Many, by function |
| OKRs | Time-bound goals with measurable key results | A few per team per quarter |
They work together, not against each other. The North Star is the direction, input metrics are the levers, KPIs are the health check, and OKRs are the goals for this quarter, often expressed as movements in input metrics.
When a North Star is a bad idea
Very early products with no proven value, where you do not yet know what users get from you. Multi-sided businesses where one number would hide problems on one side, for example supply versus demand. And any situation where a single metric would tempt people to game it at users’ expense. In those cases use a small set of metrics with clear guardrails instead.
Setting targets and a review rhythm
A North Star without a target is a number, not a goal. Set targets for the input metrics first, based on your current baseline and what recent changes have achieved, and let the North Star target follow from them. Review the inputs weekly, the North Star monthly, and the choice of North Star itself once or twice a year. If you find yourself changing the metric because it looks bad, stop: that is the moment it is most useful.
How it connects to OKRs: a worked link
| Level | Example (learning app) |
|---|---|
| North Star | Weekly learners who complete a lesson and improve |
| Objective (this quarter) | Make the first week so good that new learners stay |
| Key result 1 | First-lesson completion from 55% to 70% |
| Key result 2 | Return within 3 days from 35% to 45% |
| Guardrail | Practice-score quality does not fall |
The key results are movements in input metrics. That is what keeps quarterly goals connected to the one number that matters, instead of drifting into a list of unrelated targets.
Three traps that quietly wreck a North Star
Vanity: total downloads or registered users, which only ever go up. Lagging only: choosing something like revenue and having no leading input to steer by. Unowned inputs: a beautiful metric tree in which no team is actually responsible for any branch. The fix for each is the same: tie the metric to user value, break it into leading inputs, and give every input an owner by name.
Common mistakes
Choosing revenue (it lags and hides user value). Choosing an activity number that can be inflated. Picking one without input metrics, so nobody knows how to move it. Changing it too often, or never revisiting it. Treating it as a slogan instead of a decision tool. And in interviews: giving a North Star with no reasoning about why it captures value. The 50 question bank includes a few of these.
See also: RICE for deciding which ideas to bet on, and the roadmap guide for turning input metrics into a plan.
Frequently asked questions
What is a North Star Metric?
The single metric that best captures the core value users get from your product and predicts long-term business success, such as successful transactions per week for a marketplace.
How do you choose a North Star Metric?
Define the core value users come for, list candidate metrics, test each against five properties (reflects value, predicts revenue, measurable, actionable, hard to game), pick one and break it into input metrics.
Is revenue a good North Star Metric?
Usually not. Revenue is a lagging result, not a measure of user value, and it cannot easily guide day-to-day product decisions.
What is the difference between a North Star Metric and a KPI?
A North Star is one number reflecting user value that steers the whole team. KPIs are many health measures across functions, such as revenue, churn and cost.
Want this sharpened for your specific situation?
I take on a small number of career calls and resume reviews each month.
See how we could work together