North Star Metric
A North Star Metric is the single measure that best captures the core value a product delivers to its customers. Popularized by growth practitioner Sean Ellis and formalized in Amplitude's North Star Framework, it gives the whole company one shared outcome to grow, supported by a small set of input metrics that individual teams can influence directly.
How a North Star Metric Works
Ellis describes the North Star as the metric that best captures the core value a product delivers, and argues that growing it is the key to sustainable growth. It counts value received by customers, not value captured by the business, which is why revenue itself is a poor choice: revenue lags behind value and can rise for reasons that do not help customers.
Amplitude's playbook gives three tests for a good North Star. It should:
- Reflect customer value: it rises when customers get what they came for.
- Represent the product strategy: it expresses the bet the company is making.
- Lead revenue: it predicts future business results instead of reporting past ones.
The metric is then broken into three to five input metrics, the factors the team believes most directly drive it, such as breadth of use, depth of use, frequency or efficiency. Teams pick inputs they can move with their work, which turns one company-level number into a set of concrete targets.
Amplitude's examples include "orders delivered" for a grocery delivery app and, for a subscription software product, "trial accounts with more than three users active in week one."
Why a North Star Metric Matters
Without a shared outcome, each team optimizes its own numbers, and the results can conflict: marketing grows sign-ups, product grows feature usage, and nobody owns whether customers succeed. A North Star connects that work to one measure of customer value. It also helps teams avoid vanity metrics, such as total registered users, that grow while the product is failing.
A single number can be gamed or distorted, so teams usually pair it with a guardrail metric, such as churn or support tickets, that warns when growth is coming at the expense of quality.
North Star Metric Example
A team building a collaborative research repository chooses "weekly active projects with at least three contributors" as its North Star. It reflects the core value, shared insight across a team, and it should lead renewals. The inputs are new projects created, invitations accepted, insights added per project and contributors returning each week. The onboarding team targets invitations accepted, while the editor team targets insights added. Total sign-ups, the old headline number, becomes a secondary metric because it rose even when projects sat empty.
To connect metrics like these to roadmap choices, see how to map product health metrics and user behavior to roadmap decisions.
North Star Metric vs. OKRs
The North Star is a lasting measure that changes only when the strategy changes. OKRs (objectives and key results) are time-bound goals, usually set each quarter. The two work together: a team's key results often target the input metrics that move the North Star.