North Star Metric

Definition: The single metric a team agrees best captures the core value a product delivers to users, used to align an entire organization around one shared measure of success.

How It Works

• Chosen to correlate strongly with long-term business success, not just an easy-to-move vanity number
• Sits above individual team metrics: a growth team, a retention team, and an engineering team can each move it in different ways
• Differs from revenue. Revenue is an outcome; a North Star Metric usually captures the user behavior that predicts revenue before it shows up on a balance sheet
• Decomposes into a small set of input metrics, each ownable by a different team, so the single number still maps to concrete, actionable work
• A good candidate reflects value delivered to the user, not just activity generated by the company (like emails sent or notifications pushed)
• Different product types tend toward different shapes of North Star: frequency-of-use metrics for consumer apps, workflow-completion metrics for B2B tools, transaction volume for marketplaces
• Reviewed periodically. A metric that made sense for an early-stage product can stop reflecting real value once the product matures
• Usually leading, not lagging: it should move before revenue does, giving teams an early read on whether the business is healthy
• Needs to be measurable reliably and frequently (daily or weekly), or teams can’t actually use it to steer near-term decisions
• Works best paired with a small set of input metrics rather than standing alone, since the single number alone doesn’t say what to do next
• Guardrail metrics are tracked alongside it, so a team can’t inflate the North Star at the expense of something the company also cares about, like trust or margin
• Works alongside, not instead of, financial metrics: a healthy North Star Metric should eventually show up in revenue and retention numbers too
• Typically owned by a cross-functional group (often called a growth council or metrics council), not by a single team, to keep any one function from steering it in isolation
• Best introduced with a clear owner and a regular review cadence (often weekly), or the number quietly drops out of everyday decision-making within a quarter

Under the Hood

Each branch is a lever a specific team owns. Growth owns acquisition and retention, lifecycle marketing owns re-engagement, and the recommendations team owns discovery quality, but all three ladder up to the same top-line number. This is the actual mechanism that makes a North Star Metric more than a slogan: every team can point to the exact branch of the tree their roadmap is meant to move.

Worked example: decomposing a North Star Metric

Given a hypothetical music app with:

• 10,000,000 weekly active users
• 5 sessions per user per week
• 12 minutes average session length

Step, the North Star (weekly listening minutes) is the product of its three inputs:

North Star = Active Users x Sessions/User x Avg Session Length
North Star = 10,000,000 x 5 x 12
North Star = 600,000,000 minutes/week

Step, test a lever: improving recommendation quality lifts average session length from 12 to 13 minutes, holding the other two inputs flat:

New North Star = 10,000,000 x 5 x 13 = 650,000,000 minutes/week

Answer: an 8.3% gain in session length alone moves the North Star by 50,000,000 minutes a week, roughly an 8.3% lift overall, showing the recommendations team exactly what its work is worth in top-line terms.

Worked example: comparing two levers

Given the same baseline, compare that recommendation improvement against a retention push that raises active users from 10,000,000 to 10,300,000 (holding sessions and length flat):

New North Star = 10,300,000 x 5 x 12 = 618,000,000 minutes/week

Answer: the 3% user growth adds 18,000,000 minutes, less than half of what the 1-minute session-length gain added. This is exactly the kind of comparison a North Star decomposition is built to make visible across teams working on entirely different levers.

Choosing between candidate metrics: a useful test is asking whether the metric could go up while users are actually getting less value.

• “Total signups” fails this test: a spike from a marketing campaign says nothing about whether those users found the product useful
• “Time spent” is a mixed signal: it can reflect real engagement, or it can reflect a confusing interface that takes longer to get anything done
• “Weekly active users completing a core action” tends to pass, since it requires the user to have actually done the thing the product exists for

Why It Matters

• Keeps teams from optimizing for numbers that look good in a local dashboard but don’t reflect whether users are actually getting value
• Gives otherwise-independent teams (growth, retention, engineering) one shared target instead of competing local goals
• Makes trade-off conversations concrete: a feature that raises signups but doesn’t move the North Star is worth questioning
• Gives leadership one number to check on that summarizes product health, instead of reconciling a dozen disconnected dashboards
• Makes prioritization faster in day-to-day roadmap debates: a proposal either has a credible story for moving one of the input metrics, or it doesn’t
• Helps new hires understand what actually matters within their first week, instead of absorbing it slowly through osmosis over months
• Gives a growing company a way to scale decision-making without every decision routing back through a single founder or executive

Common Pitfalls

• Picking a metric that’s easy to inflate without delivering more value, like “signups” or “downloads” instead of ongoing active use
• Choosing a metric so broad (like total revenue) that no single team can see how their work actually moves it
• Treating the North Star as fixed forever. A maturing product often needs to revisit whether its chosen metric still reflects real value
• Confusing a North Star Metric with a KPI dashboard, tracking dozens of numbers with equal weight instead of rallying around one
• Setting a North Star that conflicts with near-term revenue pressure, then quietly abandoning it under quarterly pressure
• Picking a metric that can be gamed by a single lever (like time spent, which can be inflated by making the product harder to use efficiently)
• Choosing a metric that only reflects one side of a two-sided marketplace (bookings without accounting for host supply, for instance) and missing structural imbalance
• Letting the metric go stale after a pivot, so the org keeps optimizing for a definition of value the product no longer actually delivers
• Rolling it out without teaching teams how their day-to-day work actually connects to it, so it becomes a slide in a deck rather than a working tool
• Setting it top-down without input from the teams expected to move it, so it never actually changes how they prioritize work
• Chasing the North Star at the expense of a guardrail metric, like driving up time spent through dark patterns that quietly erode trust
• Reporting the metric only at the company level, so individual teams can’t see their own contribution and lose motivation to move it

Comparison

	North Star Metric	Vanity Metrics	OKRs
What it is	One metric reflecting real user value	Numbers that look good but don’t predict value (signups, downloads, page views)	A goal-setting framework pairing objectives with measurable results
Time horizon	Ongoing, product-level	N/A, often trails actual value	Usually quarterly cycles
Purpose	Align the org around what matters	Often used in marketing or investor decks	Translate strategy into a specific, time-bound set of goals
Changes how often	Rarely, only as the product matures	Whenever it’s convenient to report	Every cycle, by design
Overlap	Can become a Key Result inside an OKR	Actively avoided as a North Star candidate	Can include the North Star Metric as one Key Result
Risk if misused	Low, designed to resist gaming	High, easy to inflate without real value	Medium, can be gamed by sandbagging targets
Who owns it	Cross-functional metrics council	Whoever is reporting the number	Individual teams, per objective

Example

Airbnb’s widely reported North Star Metric is nights booked, not signups or listings, since that number reflects real value delivered to both guests and hosts simultaneously, and it directly predicts revenue without being revenue itself. A host only earns and a guest only benefits once a booking actually results in a completed stay, which is why the company has publicly discussed the metric as a proxy for the health of its entire marketplace.

Facebook’s early growth team, led by Chamath Palihapitiya, is well known for finding that new users who added 7 friends within 10 days of signing up were far more likely to stick around long-term. That benchmark, “7 friends in 10 days,” became a north-star-style activation target that reshaped onboarding around driving toward that specific behavior instead of raw signup counts. It’s often cited in growth and product circles as an early example of finding the leading indicator behind a broader North Star, rather than just staring at the top-line number itself.

Related Terms

• Product-Market Fit — a North Star Metric is often the clearest signal that fit has been found
• A/B Testing — the method used to test whether a specific change actually moves the North Star
• OKRs (Objectives and Key Results) — the North Star often becomes a Key Result at the company level
• Google Analytics — common tooling for tracking and reporting the North Star Metric and its inputs
• Mixpanel — common tooling for tracking and reporting the North Star Metric and its inputs
• Prioritization Frameworks — used alongside the North Star to decide which input-metric bets to fund