North Star Metric

The North Star Metric is the one number a product team uses to align decisions. Choosing it well is the most strategic decision a growth team makes; choosing it badly produces years of optimized noise.

Origin

The North Star concept emerged from growth practitioners at companies like Facebook, Airbnb, and Spotify in the early 2010s, codified in Sean Ellis's book Hacking Growth (2017) and Amplitude's North Star Playbook (2019). The framework grew out of Ellis's earlier work on "product-market fit" — once you have it, the question becomes how to grow it; the North Star is the metric that says whether you're growing the right thing.

Inputs feed the North Star; the North Star feeds revenue indirectly, by way of customer value.

What makes a good North Star

A useful North Star Metric satisfies three tests: it captures the customer value the product delivers, it correlates with long-term revenue, and it is something the team can directly influence through their work. "Revenue" itself usually fails the third test — it's an output of many things including pricing decisions and macro trends. "Daily active users" usually fails the first test — it captures usage but not value (a user can be active and unhappy).

Famous examples: Spotify's "time spent listening" (depth/frequency); Airbnb's "nights booked" (transactions completed); Facebook's "daily active users with seven friends added" (an early activation-shaped North Star); Slack's "messages sent in active workspaces."

The structure: one star, many inputs

The North Star sits above 3-5 input metrics that drive it. The Amplitude playbook standardizes these as breadth (how many people), depth (how much per person), frequency (how often), and efficiency (how successfully). Each input metric is owned by a team or sub-team; together they roll up to the North Star.

For Slack: messages sent in active workspaces could decompose into number of active workspaces (breadth), users per workspace (depth), messages per user (frequency), and percentage of messages in conversations rather than in announcement channels (efficiency / depth quality).

When North Star is the right tool

North Star is most useful for: product-led growth companies aligning a large product/eng/data org around one number; post-product-market-fit growth phase when the question is no longer "are we building something people want" but "how do we deliver more of it to more people"; cross-functional alignment between product, marketing, and customer success.

It's a poor fit for: pre-product-market-fit companies (the question is qualitative, not quantitative); B2B sales-led companies where ARR is the obvious metric; or services businesses where the value delivered varies enormously per engagement.

How to choose a North Star

Start from value delivered. What is the moment in your product where the customer experiences the value? Note that — not the moment of payment.
Express it as a leading indicator of revenue. A North Star that doesn't predict revenue 12-18 months out isn't doing its job. Test the correlation against historical data.
Test the perversion failure mode. If the team optimized this metric and ignored everything else, would the company benefit or suffer? Daily active users optimized perversely produces dark patterns; messages-sent-in-active-workspaces is harder to game in customer-harming ways.
Make it actionable. Each function should be able to point to specific work that moves the metric. If marketing can move it but product can't (or vice versa), the metric is too narrow.
Keep it stable. The North Star should change rarely — it's the strategic anchor. Input metrics evolve as the team learns; the star itself shouldn't.

Worked example: a video editing tool

A consumer video editing app debates its North Star. Three candidates:

Daily active users. Easy to measure, easy to grow with notifications, but uncoupled from value. A user opening the app to watch other people's videos isn't getting the value that justifies a subscription.
Videos exported. Strong value-correlation; a user who finishes and exports a video has experienced the full product value. Easy for product to influence (faster export, fewer crashes); easy for marketing to influence (better onboarding, template gallery).
Subscription revenue. Easy to measure but lagging — pricing changes, churn, and acquisition all affect it independently of the product experience.

Choice: "weekly videos exported per active workspace" — captures depth (engagement) and value-completion (the user finished something). Decomposed: weekly active workspaces (breadth), videos started per workspace (depth), share of started videos that are exported (efficiency). The team can move all four; together they predict subscription growth six months out.

How North Star goes wrong

Picking a vanity metric. Sign-ups, page views, downloads — easy to grow, weak correlation to value. The team optimizes the metric without growing the business.
Picking the revenue. ARR or MRR is the goal, not the lever. A North Star is what you optimize so that revenue follows.
Too many "North Stars." A product with three North Stars has none. The point is single-metric alignment.
Changing it frequently. The North Star sets strategic direction; flipping it every quarter signals confused strategy and confuses the team.
Ignoring counter-metrics. Every North Star can be optimized in customer-harming ways. Pair with counter-metrics — for engagement North Stars, satisfaction; for transaction North Stars, refund rate.

Critique

The North Star Metric framework has been criticized for being a creative repackaging of older balanced-scorecard concepts. The substantive critique is that single-metric optimization is dangerous in a complex business — the same critique that applies to OKRs and to MBO before them. The defense is that the North Star is supposed to be a focusing device, not the only metric the company tracks, and that the mistake is treating it as comprehensive rather than as a primary anchor.