The North Star Metric Framework

What a North Star Metric is actually for

A North Star Metric (NSM) is the single measure a company chooses to represent the core value it delivers to customers, used as the organizing metric that every team's work is expected to ultimately move. It is deliberately not revenue — revenue is an outcome of value delivered, often lagging and easy to inflate short-term in ways that damage the underlying product (aggressive upsells, dark-pattern pricing). The NSM is meant to sit upstream of revenue: Airbnb's historically cited North Star was nights booked, Spotify's was time spent listening, Slack's was messages sent between teammates. Each of those captures the moment the product actually delivers value to a user, not the moment the company gets paid for it — the belief being that if that value metric grows durably, revenue follows.

What makes a metric a good candidate

A usable North Star Metric needs to pass several tests simultaneously. It must reflect customer value, not just company convenience — "logins" is a weak NSM because a user can log in without getting any value, while "projects completed" ties directly to the outcome the user wanted. It must be a leading indicator of revenue rather than revenue itself, so teams can act on it before the quarter's numbers are already locked in. It needs to be actionable — teams need to be able to point to specific levers (onboarding changes, feature launches) that plausibly move it, rather than it being a macro number nobody directly influences. And it should be measurable reliably and frequently, ideally in a single number everyone in the company can state without a dashboard, because its entire value is as a shared, legible rallying point.

North Star Metric candidates by company type

Input metrics: the levers underneath the headline number

A North Star Metric is almost never directly actionable on its own — it's too aggregate for any single team to move it by working on it directly. The practical structure is a North Star sitting atop a small set of input metrics, each owned by a specific team, that mechanically roll up into the North Star when they improve. For a NSM like "weekly active collaborators," the input metrics might be new-user activation rate, feature adoption depth, and churn/reactivation rate — each with a clear owner and each a lever a team can actually pull. The North Star gives the company a shared destination; the input metrics are the map of roads that actually get there, and they're where OKRs and roadmap prioritization should live day to day.

Common mistakes teams make choosing one

The most frequent error is picking a metric that's easy to game without actually delivering value — "time on app" can go up because the product got more confusing to navigate, not more valuable. A related mistake is choosing a vanity metric that only ever goes up (cumulative signups, total downloads), which looks great on a chart but can't actually signal decline, so it stops being useful as an early-warning system the moment growth slows elsewhere. Teams also frequently pick a metric too early, before the product's core value loop is even settled, and then anchor the whole org around a number that has to be scrapped a few months later — it's reasonable for an early-stage product to not yet have a stable NSM. Finally, some organizations pick a NSM and then never actually route planning or incentives through it, so it becomes a slide in a deck rather than the thing that actually governs prioritization.

What's next

Once a North Star Metric is chosen, mapping it onto the classic acquisition-through-revenue stages gives teams a shared vocabulary for where in the user lifecycle their input metrics actually live.

Next: Pirate Metrics (AARRR) →