North Star metric
A North Star metric is one number a product team adopts to express the value its users receive, in a way that also predicts the company's long-term success. A few input metrics the team can influence directly support it, and guardrail metrics make sure nothing important degrades along the way. Typical examples count recurring valuable actions, such as teams collaborating on a document each week, rather than revenue or sign-ups.
Why it matters for a PM
A good North Star aligns teams that would otherwise optimize conflicting numbers, and it gives a PM a simple test for any roadmap item: which input does it move, and how would we know? Choosing it forces an explicit discussion of what value means for users, which is often the real benefit of the exercise.
Example
A team collaboration tool picks “number of teams that edit a shared document at least three days a week” as its North Star. Input metrics include invitations accepted and documents created from templates; guardrails include page load time and support tickets per active team.
Key points
- It measures delivered value, ideally as a frequency over time, not a one-off event.
- Input metrics break it down into levers that specific teams can own.
- Guardrail metrics (quality, churn, complaints) prevent gains bought at the expense of users.
- It changes rarely, but deserves a fresh look when the strategy or the business model shifts.
Common mistakes
- Picking revenue or total sign-ups, which lag behind and are hard to act on.
- Choosing a vanity metric that grows without telling you anything about value.
- Having several North Stars, which defeats the purpose of a shared focus.
- Setting it once and never connecting it to roadmap decisions.
Go further with Module
The courses and lessons that cover this concept: