A North Star metric should focus your entire team on a single measure of the value your product creates. Most don't. They either measure business outcomes instead of user value, or they're so vague they're impossible to act on. Here's how to get it right.
The North Star metric concept comes from the observation that the most effective product teams organize around a single number that captures the core value their product creates for users. The logic: if you can identify the metric that best represents "users are getting value from this product," and if you can make your entire team responsible for moving it, you get alignment without constant coordination overhead.
In theory, elegant. In practice, most North Star implementations fail because teams choose the wrong metric — or choose the right metric but fail to connect it to the daily work of the team.
What Makes a Good North Star Metric
A good North Star metric has four properties:
It measures user value, not business outcomes. Revenue is not a North Star metric. Revenue is what happens when you create user value at scale. The North Star should measure the value creation, not the result of it. Airbnb's "nights booked" captures value for both hosts and guests. Spotify's "time spent listening" captures music discovery and enjoyment. These are user behaviors that indicate value, not financial results.
It's a leading indicator of business health. When the North Star goes up, business outcomes — revenue, retention, referrals — should eventually follow. When it goes down, they should eventually fall. If there's no causal connection between your North Star and business outcomes, you've picked the wrong metric.
It's specific enough to be actionable. "Users get value" is not a North Star metric. It's an intention. The metric needs to be specific enough that when you look at it, you know whether it went up or down and you can reason about why. "% of users who complete a project within their first week" is actionable. "User satisfaction" is not.
It's understandable by everyone on the team. If an engineer has to ask what the North Star metric means, it's too complex. The North Star should be simple enough that every person in the company can hold it in their head and reason about how their work affects it.
The Process for Finding Yours
Start by asking: what's the moment when a user gets genuine value from our product? Not discovers it. Not signs up for it. The moment the core value proposition is delivered. For a task management app, it might be when a user completes their first important task. For a collaboration tool, it might be when a team successfully ships something together. For a marketplace, it might be when a transaction successfully completes for both parties.
Find that moment. Then find a metric that captures how often it's happening, for how many users, with what frequency. That's your North Star candidate.
Test it against the four criteria above. Does it measure user value? Does it lead to business health? Is it specific enough to be actionable? Is it understandable? If it fails any of these, refine it until it passes all four.
Then comes the harder part: connecting the North Star to the team's daily work. The North Star is a lagging indicator for teams — it captures the accumulated result of many decisions and changes. To make it useful for day-to-day work, you need to identify the input metrics that drive it. What user behaviors, product features, and operational factors are the key drivers of the North Star? Those become the focus of the team's weekly work.
Finding your North Star?
Identifying the right North Star metric and connecting it to the team's work is one of the most valuable things you can do for product clarity. I've helped multiple teams do this well. Let's talk about your product and find yours.
Work with Yogesh →