Skip to content
Back to Growth & Acquisition

North-Star Metric

Pick the single metric that best captures the core value your product delivers to users.

Why

A north-star metric (NSM) aligns the entire company around one definition of growth, ending debates about which dashboard matters this week. It forces you to define what 'value delivered' actually means for your users, not what 'revenue extracted' means for you — and products that grow sustainably optimize for the former. Every team can map their weekly work to the NSM: does this feature, fix, or campaign move it? If not, it is a candidate for deprioritization. Without an NSM, teams optimize local metrics that conflict (e.g. sales pushes discounts while retention fights churn), and the company moves in circles.

When

When you have product-market fit but lack a shared growth definition, or when different teams report conflicting 'we grew' claims. Set it once, review quarterly.

How

1. List 5-10 candidate metrics that represent value delivered (not revenue collected) — e.g. weekly active users who performed the core action, documents created, messages sent
2. Score each on: (a) does it measure real value? (b) does revenue correlate with it? (c) can the whole team influence it weekly? (d) is it leading not lagging?
3. Pick the one that scores highest — there is only one NSM, not three
4. Decompose the NSM into a metric tree: NSM = (new users) × (activation rate) × (retention) × (referral multiplier) × (monetization)
5. Assign each tree node to an owning team with a weekly target
6. Instrument the NSM in your analytics tool with a single source-of-truth dashboard
7. Run weekly growth reviews against the NSM and its tree, not vanity metrics
8. Re-evaluate the NSM quarterly — it should change only on a major strategy pivot

Example

# Slack's North-Star Metric: "messages sent per active user per day"
# Not: DAU (too broad), not MRR (lagging), not signups (vanity)

# Metric tree decomposition
NSM = weekly_active_teams
     × messages_per_user_per_week
     × percent_users_engaged_in_team
     × (1 + referral_coefficient)

# Weekly growth review agenda
1. NSM this week vs last: 12.4 → 12.7 (+2.4%)
2. Tree node that moved most: activation rate +5%
3. Tree node that regressed: referral -0.3%
4. This week's experiments: 3 shipped, 1 won, 2 inconclusive
5. Next week's bets: 2 on referral, 1 on retention

Common Problems

  • ⚠Picking revenue as the NSM — it is lagging, narrow, and makes the team optimize extraction over value, which eventually kills growth.
  • ⚠Having 'three north stars' for three teams — that is three stars pointing in three directions, i.e. no alignment at all.
  • ⚠Choosing a metric you cannot measure weekly, so the team flies blind between monthly board reports.
  • ⚠Never decomposing the NSM into a tree, so no team knows which lever is theirs to pull.

Best Practices

  • ✓Choose a leading indicator of value delivered, not a lagging indicator of revenue collected — the former predicts the latter, not vice versa.
  • ✓Decompose the NSM into a metric tree and assign each node to one owning team with a weekly target; this is what makes the NSM actionable.
  • ✓Review the NSM and its tree every single week; a metric reviewed monthly is a metric ignored for 29 days.
  • ✓Re-evaluate the NSM only on a major strategy pivot — changing it every quarter from whimsy destroys the long-term signal.