The Idea Behind a Single Metric
The North Star Metric is the one number that best captures the value your product delivers to users, and the one most tied to your long-term business success. The idea, popularised by Sean Ellis and Amplitude, is that focusing the entire team on a single metric produces clarity, alignment, and faster progress than tracking many metrics without prioritising one.
When teams pick a good North Star, the effect is real. Engineering, design, marketing, and sales all know what they are working toward. Trade-offs are easier because the criterion for evaluating them is shared. The team has a clear way to know whether they are succeeding.
When teams pick a bad North Star, the effect is also real, and worse. The whole organisation optimises for the wrong thing. Bad decisions get made because they improve the metric. The product becomes optimised for a number rather than for users. This article is about how to pick a North Star well, the most common mistakes, and how to use it without letting it distort the work.
What a Good North Star Looks Like
Good North Stars share several characteristics. None on its own is sufficient, but together they form a useful filter.
It Reflects Real Value Delivered to Users
The metric should track something users actually care about. If your North Star can go up while users get worse outcomes, the metric is wrong. The number should be a measure of users getting more of what they came for, not just doing more on your platform.
It Predicts Long-Term Business Success
If the North Star goes up consistently, the business should do well over time. There should be a credible mechanism by which user value translates into business value. Without this, you may have a metric that grows without producing revenue.
It Is Specific and Behaviour-Based
Engagement is too vague. Songs played per week per active user is specific. The metric should describe a specific user behaviour that captures the core value, not a general feeling. Specific metrics drive specific work.
It Includes a Time Component
Cumulative metrics (total ever) only go up, regardless of current health. Period-based metrics (per week, per active user) can go up or down and reflect current reality. North Stars almost always have a time component because the team needs to see whether things are improving now.
The Team Can Move It
Some metrics are mostly outside the team's control (macro-economic factors, regulatory changes). These don't make good North Stars because the team can't do much about them. The North Star should be something where team work demonstrably moves the number.
Examples by Product Type
Different product types tend to have different shapes of North Star. The pattern repeats across companies in similar businesses. These are common patterns, not company-specific claims.
Product Type Likely North Star Pattern
Communication apps Messages sent per week per active user
Content platforms Time spent / pieces of content consumed per week
Marketplaces Successful transactions per period (matched on both sides)
Productivity tools Active users completing the core action weekly
Subscription content Days per week active among subscribers
B2B SaaS Weekly active users at customer accounts (with retention)
E-commerce Repeat purchases or order value per active customer
Travel / booking Successful trips booked
Notice the pattern. None of these are total cumulative numbers. None are simple sign-up counts. All measure behaviour that represents real user value, normalised by time and often by user. This shape is what makes a North Star a North Star.
Common Mistakes in Choosing
Mistake One: Picking Revenue Directly
Revenue is the ultimate output, not the right North Star. Optimising for revenue directly often pushes teams toward tactics that boost short-term revenue at the expense of long-term user value: aggressive pricing, dark patterns, monetisation that frustrates users. The North Star should be the user behaviour that, when it grows, produces revenue. Track revenue separately as the lagging confirmation.
Mistake Two: Picking a Vanity Metric
Total registered users. Total downloads. Page views. These look impressive and tell you almost nothing about whether the product is working. They can rise during decline. They are vanity, not value. North Stars must be value metrics.
Mistake Three: Picking a Metric That Includes Bad Behaviour
Some metrics treat all engagement as good. Time spent on the site, for example. Users scrolling because they couldn't find what they wanted is bad engagement, but the metric doesn't distinguish. Picking such a metric optimises for behaviour the team would not endorse if asked directly. The North Star should reflect successful engagement, not raw engagement.
Mistake Four: Picking Multiple North Stars
Some companies pick three or four "North Star metrics." By definition, you can't have multiple North Stars. The whole point is one number to focus on. Multiple metrics produce ambiguity about trade-offs. Pick one; track others as supporting metrics.
Mistake Five: Picking a Metric With Long Latency
Some metrics take months to move (long-term retention, lifetime value). Picking these as North Stars produces frustration: the team works for months without seeing the metric move. Better to pick a leading metric (an early behaviour predicting the long-term outcome) as the North Star and track the long-term outcome as confirmation.
Process for Picking Your North Star
Picking the right North Star takes deliberate work. Here is a sequence that has produced reliable results.
Step One: Identify the Core Value
What is the most valuable thing your product does for users? Answer this in plain language, in user terms, not in feature terms. Helps small businesses get paid faster. Helps designers ship more polished work in less time. Helps people find homes that suit their lives. Be specific.
Step Two: Identify the Behaviour That Reflects It
What user behaviour, when observed, indicates that this value is being delivered? Invoices sent and paid. Designs published to clients. Saved homes that lead to tours. The behaviour is observable and measurable.
Step Three: Convert to a Per-Period, Per-User Number
Frame the behaviour as a rate. Per week. Per month. Per active user. The framing prevents cumulative inflation and lets the metric move both up and down. Invoices sent and paid per active business per week.
Step Four: Test Against the Three Criteria
Does this metric reflect real user value? Yes, it captures the core thing users came for. Does it predict business success? Yes, more invoices sent and paid means more revenue (through subscription or transaction fees). Can the team meaningfully influence it? Yes, through onboarding, feature development, and retention work. If all three pass, the metric is a candidate.
Step Five: Pressure-Test
Imagine the metric goes up significantly. What does that mean? Is it possible to game without delivering more user value? If yes, refine the metric. Invoices sent could be gamed by sending more invoices for the same value; invoices sent and paid can't. The pressure-test reveals weaknesses.
Step Six: Validate With Historical Data
Look at past periods. When this metric was high, was the business doing well? When it was low, was the business struggling? If the metric correlates with business outcomes historically, that is good evidence it captures the right thing.
Inputs and Outputs
Once you have a North Star, you also want to track the inputs that drive it. The North Star is the output. The inputs are the levers the team can pull to move the output.
A Useful Mental Model
If your North Star is weekly active users , the inputs are: new users who arrive, percentage who activate, percentage who become weekly active, and percentage who churn from weekly active. Move any of these inputs and the output moves. Tracking the inputs lets you diagnose which lever is most useful at any given time.
A Decomposition Pattern
Many North Stars decompose into a few input metrics. Successful transactions per week = (new users per week) × (% who complete first transaction) × (return rate and frequency). Each factor is a separate metric you can measure and influence. The decomposition makes the North Star less mysterious; you can see what drives it.
Don't Replace the North Star With Inputs
Some teams decompose the North Star and then forget about the North Star itself. They optimise inputs in isolation and the North Star drifts. The discipline is to keep the North Star as the headline and use inputs for diagnosis and tactics.
Using the North Star Without Distorting Work
A common danger of North Star thinking is that the team starts optimising for the metric rather than for users. Goodhart's Law applies: when a measure becomes a target, it ceases to be a good measure. A few practices help avoid this trap.
Pair the North Star With Counter-Metrics
Counter-metrics are metrics that should NOT decline as the North Star grows. If your North Star is weekly active users , counter-metrics might include user satisfaction and support volume. If WAU grows but satisfaction tanks, the team has gamed the North Star at the expense of users. The counter-metrics protect against distortion.
Track Quality of the Behaviour, Not Just Volume
If the North Star is a behaviour count, also track the quality of those behaviours. Messages sent doesn't distinguish meaningful messages from spam. Adding a quality filter (messages received and responded to, for instance) ensures growth is real, not gamed.
Discuss the Metric, Not Just Optimise It
When the metric moves, ask why. Did we ship something that produced the change? Was it seasonal? Was it a quality issue masquerading as growth? The discussion keeps the team grounded in user reality, not just the number.
Be Willing to Update the North Star
If the North Star starts producing bad behaviour or no longer captures what matters, change it. North Stars are not eternal; they should evolve as the product matures and the strategy shifts. The frequency of change should be low (years, not months), but the willingness to update should be there.
Communicating the North Star
A North Star only works if the whole organisation knows it, understands it, and uses it. The communication work is as important as the choice.
Make It Visible
Display the metric publicly. In a dashboard, in all-hands meetings, in onboarding documentation. Repetition matters. Within a few months, every employee should know the metric and roughly where it is.
Tie Decisions to It
When making strategic decisions, name how they affect the North Star. This investment improves activation, which feeds the North Star. The discipline of explicit linkage trains the team to use the metric as a guide.
Celebrate Movement
When the North Star moves up, celebrate. Tell the story of what shipped and how it contributed. The recognition reinforces the metric's importance and motivates further work.
Be Honest About Decline
When the North Star moves down, don't hide it. Discuss openly. Diagnose the cause. The team builds trust by acknowledging reality; hiding declines erodes credibility.
Common Mistakes in Use
Mistake One: Setting It and Forgetting It
Some companies pick a North Star, announce it, and then rarely reference it again. Without active use, the North Star is just a poster. Reference it in decisions, in reviews, in goal-setting. The repetition is what makes it matter.
Mistake Two: Punishing People for Misses
If teams are punished for the North Star not moving, they will optimise for it in distorting ways. Treat the North Star as a shared compass, not a stick. Diagnose misses honestly; learn rather than blame.
Mistake Three: Letting It Replace Strategy
The North Star supports the strategy; it doesn't replace it. Strategy tells you what game you are playing; the North Star tells you the score. A team that obsesses over the North Star but loses sight of strategy may grow the metric in directions that don't serve the long-term plan.
Mistake Four: Not Adapting Over Time
What was the right North Star for an early-stage product may not be right at scale. As the product matures, the North Star should evolve. Treat it as something to revisit every year or two, not as fixed forever.
A Final Word
A good North Star clarifies the team. A bad one distorts it. The choice is consequential and worth real deliberation. Invest the time. Pressure-test the candidates. Validate against history. Pair with counter-metrics. Communicate widely. Use in decisions. The discipline pays off in alignment and clarity that no number of dashboards can replace.
If you don't have a North Star yet, take this article as a prompt to develop one. Spend a week or two on it. Run the process described above. Test the candidates. Pick the best. Communicate it. Then start using it in daily work. Within a few months, you will see the difference: faster decisions, clearer trade-offs, more aligned teams. The investment is small; the compounding effect is large.
Key Takeaways
- A North Star Metric is the single number that best captures user value and predicts business success. One metric, deliberately chosen.
- Good North Stars are specific behaviours, expressed as rates per period per user, that the team can move and that align user and business interests.
- Common mistakes: picking revenue directly, picking vanity metrics, picking metrics that include bad behaviour, picking too many.
- Pair the North Star with counter-metrics that should not decline. Track quality, not just volume. The counter-metrics prevent distortion.
- A North Star is only useful if used. Reference it in decisions, communicate widely, celebrate movement, be honest about declines. Update it every few years as the product matures.