North Star Metrics

---

Origins

The North Star Metric concept was popularized by Sean Ellis (the author of Hacking Growth) in the early 2010s, building on earlier work by growth practitioners at Facebook, Airbnb, and Spotify.¹ The premise is simple: among the dozens of metrics a product team could track, there should be one that captures the value the product is delivering to its users. That single metric becomes the team's compass.

What Makes a Good North Star

A useful North Star Metric has three properties:

• It captures customer value. When the number goes up, customers are getting more of what they came for. It's not a vanity proxy.
• It's leading, not lagging. It predicts revenue and retention rather than recording them after the fact.
• It's actionable by the team. The team can influence it through product decisions, not just through marketing spend.

Common examples that meet all three:

• Airbnb: nights booked.
• Spotify: time spent listening.
• Slack: messages sent in active teams.
• Facebook (historical): daily active users who connected to seven friends in ten days.
• WhatsApp: messages sent per user per day.

Why a Single Metric?

The case rests on focus. Teams that try to optimize multiple metrics simultaneously make slow, hedged, ambiguous decisions. Teams that have a single North Star can ask of any proposal: does this advance our metric? The question is sharp; the answer is usually clear.

This is a deliberate simplification of reality. A product produces multiple values for multiple stakeholders. A single metric cannot capture all of that. The North Star is a working approximation — useful precisely because it's narrower than the truth.

The Trap of the Wrong North Star

Picking the wrong North Star is the most expensive mistake in the framework. Bad choices include:

• Pageviews. Easy to game by making the product worse — more clicks required to complete tasks.
• Signups. Doesn't capture whether users get value. Easy to inflate with marketing.
• Engagement-only metrics for products where engagement isn't the value (e.g., a tax tool that should be used quickly and rarely).
• Revenue itself in early-stage products where revenue lags the actual product-market fit signal.

The test for a candidate North Star: could we improve this number by making the product worse? If yes, it's not the right metric.

Supporting Inputs

A North Star Metric is usually paired with three to five input metrics — the levers the team can pull that will move the star. For Airbnb's "nights booked":

• Active listings.
• Search-to-book conversion.
• Average booking duration.
• Repeat booking rate.

The North Star is the outcome the team is trying to grow; the inputs are what the team actually works on. The pairing prevents the North Star from being too abstract to act on.

How North Stars Go Wrong

• Picked by committee. A North Star Metric chosen to satisfy every department becomes meaningless. It must reflect the product's actual value, even if that's politically uncomfortable.
• Targeted, not tracked. When the metric becomes a target, gaming starts. Track it; don't set arbitrary growth goals on it.
• Updated too often. Changing the North Star quarterly defeats its purpose. The metric should be stable over years.
• Used to override judgment. Sometimes the right product decision will hurt the North Star short-term. The metric is a compass, not a ceiling.

When To Change It

Stable doesn't mean permanent. A North Star Metric should change when:

• The product strategy fundamentally shifts (new business model, new core value).
• The metric stops being the leading indicator it once was (the product matured past the stage it described).
• The team learns the metric was actually measuring the wrong thing.

These changes are rare. A team that changes its North Star yearly probably never had a real one.

Coaching Tips

Run the "make it worse" test.

Could you improve this number by making the product worse for users? If yes, it's the wrong metric.

Pair with three to five inputs.

The North Star is the outcome; the inputs are what the team actually works on. The pairing makes the metric operational.

Resist committee picking.

A North Star designed to satisfy every department is meaningless. Pick the one that captures the product's value honestly.

Track, don't target.

Setting growth targets on the North Star invites gaming. The metric is a compass; trends are what matter.

Defend it against changes.

A North Star that shifts every quarter is wallpaper. Defend the metric unless the strategy genuinely changed.

Connect every initiative to it.

"How does this advance the North Star?" Asked of every proposal, the question shapes the backlog.

Summary

The North Star Metric is one of the most leveraged concepts in product strategy when it's chosen well — and one of the most dangerous when it's chosen badly. Picked correctly, it gives an entire organization a shared compass. Picked badly, it becomes the thing the team optimizes for at the expense of what they should be doing. The discipline is in choosing carefully, defending the choice against political compromise, and treating the metric as a signal rather than a goal.

Back to Agile Metrics