North Star Metric Builder
Define the one metric that captures the value your product delivers — then pressure-test it against the five marks of a real North Star before your team commits to it.
Build & test your North Star
A North Star Metric is the single number that best captures the core value customers get from your product — and a leading indicator of sustainable growth. Draft a candidate, score it, and map the inputs that move it.
Your North Star is the destination; input metrics are what your team actually pulls to get there. List 2–4.
Examples for inspiration
What makes a North Star real
The trap is picking a number that looks like progress but isn't. Revenue lags, total signups only ever climb, and "engagement" can mean anything. A real North Star reflects value customers actually receive, predicts revenue rather than reporting it, and moves when your team does good work.
Use it like this: one North Star for the whole product, reviewed rarely. Input metrics underneath it are what individual teams own and move week to week.
The honest caveat: no metric captures everything. The North Star focuses the org — it doesn't replace judgement, qualitative insight, or guardrail metrics that catch harm.
What a candidate metric has to survive
Most metrics that get proposed as a North Star fail on at least one of these. The builder scores your candidate against all five; here is what each one is actually checking, and the flag that tells you it has failed.
1 · It reflects customer value. When the number goes up, are customers genuinely better off — or are they simply doing more of something? The flag: if the metric can rise while customers get nothing extra, it is measuring activity rather than value. Sessions per user rises when people cannot find what they need.
2 · It leads, rather than lags. A North Star should predict revenue, not report it. Revenue, bookings and total sales are all outcomes of value already delivered; by the time they move, the decision that caused it is months old. Look for the customer behaviour that reliably happens before the money.
3 · Your team can move it. If external forces — seasonality, a partner, the wider market — drive the number more than your team's work does, it will not guide any decision. A useful test: name three things your team could ship this quarter that would visibly move it. If you cannot, it is too far from the work.
4 · It is simple and measurable. You need to be able to track it reliably today, and to explain it in one sentence to someone outside the team. A composite index with five weighted inputs may be more accurate and will still fail, because nobody will rally around a number they cannot explain.
5 · It is not a vanity metric. Total signups, cumulative downloads and page views only ever go up. A real North Star can fall when you deliver less value — that is precisely what makes it informative. If your metric structurally cannot decline, it cannot tell you anything you did not already know.
Where North Star Metrics go wrong
Picking revenue. It is the most common first answer and it fails the leading test. Revenue tells you what value you delivered in the past and gives a team no guidance about what to build. It belongs on the dashboard; it does not belong as a North Star.
Picking engagement. "Engagement" is not a metric, it is a category. Time in app is a North Star for a media product and a failure signal for a workflow tool, where the goal is to get people out faster. The word hides the decision rather than making it.
Having more than one. Two North Stars is zero North Stars. The whole point is a single number that resolves arguments when two good options compete. Input metrics are where the nuance lives — that is what the third step of the builder is for.
Changing it every quarter. A North Star should survive several years. If it keeps moving, what you actually have is a quarterly goal. That is a legitimate thing to have — it is an OKR, not a North Star.
Choosing it in a leadership offsite and announcing it. A metric nobody on the delivery team can connect to their own work gets quoted in decks and ignored in planning. Map the input metrics with the people who will pull those levers.
Common questions
How is a North Star different from an OKR? The North Star is the destination and it holds for years. OKRs are how you plan to move toward it in a given quarter. A healthy setup has one North Star and successive sets of OKRs whose key results ladder up to it.
What is the difference between a North Star and a KPI? KPIs are the set of numbers you watch to know the business is healthy — several of them, often owned by different functions. The North Star is the one you would keep if you had to drop the rest, chosen because it best captures delivered customer value.
How many input metrics should I have? Two to four. Each should be a lever your team can pull directly, and together they should plausibly account for movement in the North Star. More than four and the model stops being a guide to action.
Can a whole company share one North Star? In a single-product company, usually yes. In a multi-product company, a company-level North Star tends to be too abstract to steer any individual team — product-level North Stars that ladder into a shared company outcome work better.
What if my candidate fails one of the five tests? Fix the metric, not the score. A failure almost always points at a specific edit: narrowing the population, adding a quality threshold, or moving one step earlier in the customer journey. "Weekly active users" that fails the value test frequently becomes a usable metric as "weekly users who complete the core action."
Is anything I type stored? No. It stays in your browser.
The full method, with worked examples.
The North Star Metric guide breaks down how to find yours and avoid the classic traps — one of 156 frameworks on PM Mapped.
Read the guide → Browse all 156 →