North Star Metric

Definition: The single metric that best captures the core value a product delivers to customers, used to align teams around what matters most.

How It Works

Choosing the Metric

A good North Star Metric is chosen because it correlates with both customer value and long-term revenue, so improving it tends to improve the business overall rather than optimizing a number in isolation
It sits above vanity metrics like total signups or downloads, which can rise even while the product delivers little real value; the North Star instead reflects genuine, repeated usage
The best candidates share three properties: they reflect real customer value rather than just company convenience, they lead revenue rather than lag it, and they’re expressed as an outcome rather than an output — “weekly active meal plans created” rather than “number of recipes in the database”
It’s usually a rate or count over a rolling time window (weekly, monthly) rather than a cumulative total, since cumulative totals only ever go up and hide whether the business is actually healthy right now
Some companies distinguish between a North Star Metric (the single top-level number) and a small set of “supporting metrics” that explain why the North Star moved, avoiding the trap of trying to cram every important signal into one figure

From North Star to Inputs

Once chosen, teams break the North Star down into an “input tree” of smaller metrics they can directly influence day to day — acquisition, activation, engagement, and retention levers that each feed the top number
Individual teams then own specific inputs (a growth team owns activation rate, a product team owns feature engagement) while everyone still sees how their work ladders up to the same shared outcome
This structure is what makes the North Star more than a slogan — it becomes a literal map connecting a designer’s weekly work to a company-level number the whole leadership team watches
Some companies formalize this as a metrics tree diagram posted in every team’s planning documents, so any proposed project can be traced back to which branch of the tree it’s expected to move

Rolling It Out

A North Star Metric only works if it’s visible — most companies put it on a dashboard every employee can see, updated at least weekly, rather than burying it in a quarterly report
Leadership typically explains the “why” behind the chosen metric explicitly, since a number handed down without context is easily ignored once the initial announcement fades
The metric is usually reviewed in a recurring meeting, often weekly, where teams discuss what moved it, what didn’t, and what’s being tried next
Adoption tends to fail when the metric is introduced once and never referenced again in day-to-day prioritization conversations — it has to actually get used to decide what to build, not just displayed

What Makes a Strong North Star Metric

Property	Weak metric example	Strong metric example
Reflects value delivered	Total signups	Weekly active projects created
Leads revenue	Page views	Completed transactions
Actionable by teams	Total registered users (ever)	New users retained to week 4
Time-bound	Lifetime downloads	Weekly completed rides
Hard to game superficially	Time on site	Tasks successfully completed

A metric that fails several of these tests tends to create the wrong incentives — for instance, “time on site” can be improved by making a product more confusing to use, which is the opposite of what a North Star Metric should reward.

Beyond these five properties, a strong North Star Metric is also easy to explain to a new employee within a minute, changes at a pace that makes weekly or monthly review meaningful (not so slow that months pass with no signal, not so fast that it’s mostly noise), and has an owner — a single team or executive accountable for understanding what’s driving it, even though many teams contribute to moving it.

North Star Metric vs. Vanity Metrics

	North Star Metric	Vanity metric
What it measures	Recurring, real customer value	Surface-level activity or reach
Response to a press spike	Largely unaffected	Jumps, then fades
Correlation with revenue	Usually strong	Often weak or nonexistent
Can be gamed easily	Hard to game without real usage	Often trivially inflated
Example	Weekly active projects created	Total app downloads ever

Vanity metrics aren’t useless — they’re often good top-of-funnel indicators, and worth tracking as supporting context — but treating them as the company’s single most important number tends to reward growth that doesn’t stick.

Why It Matters

Gives a fast-growing company one shared number to rally around instead of chasing dozens of disconnected metrics that can pull different teams in different, sometimes contradictory, directions
Makes prioritization tractable: when two competing projects are proposed, the team with a clear North Star can ask “which one moves the metric more?” instead of relying purely on opinion or seniority
Creates a natural check against vanity-metric chasing, since marketing-driven signups or one-time press spikes don’t move a well-chosen North Star the way they inflate simpler counters
Gives investors and boards a single, credible signal of underlying product health that’s harder to spin than revenue alone, especially for early-stage companies not yet optimizing for revenue
Surfaces problems early — a stalling North Star Metric is often the first visible sign of a product losing Product-Market Fit, well before revenue or churn numbers would show it
Improves cross-functional collaboration, since engineering, design, marketing, and sales all have a shared definition of “winning” instead of each function optimizing its own local metric
Provides a natural anchor for setting OKRs (Objectives and Key Results) each quarter, since Key Results can be chosen explicitly because they move the North Star
Makes onboarding new employees faster, since a single well-explained metric communicates company priorities more effectively than a long list of departmental goals

Common Pitfalls

Picking a metric that’s really a vanity metric in disguise: total registered users, app installs, and pageviews all tend to rise on their own without reflecting real ongoing value — beware anything that never goes down
Choosing a metric too far removed from revenue: an engagement number that doesn’t eventually connect to monetization can rally the team around growth that never turns into a sustainable business
Setting it once and never revisiting it: the right North Star Metric often changes as a company matures — an early-stage product optimizing for activation may need a different North Star once retention becomes the bigger opportunity
Choosing a metric that’s easy to game: if a metric can be inflated through low-value tricks, like spammy notifications to boost “sessions,” teams will eventually optimize for the trick instead of the underlying value
Using a single metric that hides an important tradeoff: a North Star focused purely on growth can mask deteriorating unit economics or quality, which is why most companies pair it with one or two guardrail metrics
Picking a lagging rather than leading indicator: metrics like monthly revenue move too slowly to guide weekly decisions; a good North Star should move fast enough to give teams timely feedback
Rolling it out without buy-in: a North Star Metric imposed top-down without explaining the “why” to every team often gets treated as another dashboard number rather than a genuine organizing principle

North Star Metrics by Business Model

Business model	Common North Star	Why it fits
Marketplaces	Completed transactions or gross merchandise value	Requires both supply and demand sides functioning together
Social and communication apps	Weekly active connections or messages sent	Reflects the network actually being used, not just installed
SaaS and productivity tools	Weekly or monthly accounts completing a core workflow	Login alone doesn’t prove value was delivered
Subscription content and media	Time spent consuming content, paired with a churn guardrail	Prevents growth that’s purely attention-grabbing
Fintech and payments	Completed transactions or total payment volume	Directly proxies trust and habitual use of real money
Two-sided platforms with a supply side	Active listings paired with completed bookings	Optimizing only one side creates a false sense of health

Guardrail Metrics

Because optimizing a single number can create blind spots, most companies pair their North Star Metric with one or two guardrail metrics that must not get worse while the North Star improves.

Common guardrails include Churn Rate, customer satisfaction scores, support ticket volume, or a direct quality or safety measure specific to the product
A ride-sharing company chasing “weekly completed rides” as its North Star, for example, might guardrail against declining driver ratings, ensuring growth in ride volume doesn’t come at the cost of service quality
Guardrails don’t need their own dashboards or ceremony — they just need to be checked whenever a team proposes a change that could plausibly move the North Star at the guardrail’s expense
Without a guardrail, it’s easy for a team under pressure to hit a North Star target to find a shortcut that technically moves the number while quietly damaging the business in a way that only shows up months later
A useful rule of thumb: pick guardrails for the specific way the North Star could plausibly be gamed at this company, rather than adopting a generic industry checklist that may not match the actual risk

How to Find Your North Star Metric

List candidate metrics. Gather every metric the team already tracks or could plausibly track, without filtering yet — the goal at this stage is breadth, not precision
Score each against the value test. For each candidate, ask whether it rises specifically when customers get more value, not just when they’re more exposed to the product or the marketing funnel
Score each against the revenue test. Check historically, or reason through carefully, whether the candidate correlates with revenue growth over time rather than just raw activity
Check for gameability. Rule out any metric a team could inflate through a low-effort trick — a notification blast, a misleading prompt — without genuinely improving the product experience
Pilot it for a quarter. Track the finalist alongside existing metrics before fully committing, since a metric that looks right on paper sometimes proves unworkable once teams try to act on it week to week
Commit and communicate. Once validated, retire competing “most important metric” narratives, put the chosen North Star on a shared dashboard, and explain the reasoning behind it to the whole company

North Star Metric Across Company Stages

Stage	Typical focus	Example North Star shift
Pre-Product-Market Fit	Activation and early retention	“Users completing their first core action”
Early growth	Habitual, repeated usage	“Weekly active users completing the core workflow”
Scaling	Usage that clearly ties to revenue	“Completed transactions” or “paid seats activated”
Mature	Efficient, durable growth	Same core metric, now paired with tighter guardrails on cost and quality

The underlying metric often stays conceptually similar across stages, but what counts as “healthy” and which guardrails matter most typically shift as the company grows.

Communicating the North Star Metric Internally

State it in one sentence that any new hire could repeat back correctly after a single onboarding session
Explain not just what the metric is, but why it was chosen over the alternatives that were considered and rejected
Show the current number and its recent trend somewhere visible by default, rather than requiring people to seek it out
Revisit and re-explain it whenever it changes, since silently swapping the company’s North Star without context breeds confusion and skepticism
Connect it explicitly to team-level OKRs (Objectives and Key Results) so the link between daily work and the company number is never left implicit

Signs Your North Star Metric Might Be Wrong

Teams routinely disagree about whether a given project would move it, which usually means the metric is too abstract or too indirectly connected to day-to-day work
It moves in the opposite direction from revenue or retention for a sustained period, suggesting it’s capturing activity rather than real value
Leadership quietly stops referencing it in planning meetings a few months after launch, a strong signal it never actually became useful for decisions
It can be improved through an obvious low-effort trick (like notification spam or a misleading UI nudge) without any real change in customer behavior
Different teams report different numbers for “the same” metric because the definition wasn’t specified precisely enough — a North Star Metric needs an unambiguous, agreed-upon calculation
It stayed exactly the same through a major product change that should plausibly have moved it, suggesting it isn’t sensitive enough to reflect what the company is actually doing

North Star Metric vs. Company Mission

A North Star Metric is not the same thing as a mission statement, though the two should reinforce each other.

A mission statement is qualitative, permanent, and aspirational — it explains why the company exists at all
A North Star Metric is quantitative, revisited periodically, and operational — it’s the closest measurable proxy for whether the mission is being achieved right now
A good test of alignment: if the North Star Metric climbed to an extreme level, would that genuinely represent the mission succeeding? If not, the metric and the mission have drifted apart and it’s worth reconsidering the metric
Missions rarely need to change; North Star Metrics sometimes do, and treating the two as interchangeable is a common source of confusion when a company decides it’s time to pick a new metric

North Star Metric in Board and Investor Updates

Boards typically want to see the North Star Metric’s trend line alongside revenue and cash figures, since it’s often the earliest indicator that something in the underlying business is changing
Presenting the input tree alongside the top-line number lets a board understand not just whether the metric moved, but why, which shapes the strategic conversation far more usefully than the raw number alone
A North Star Metric that’s flat or declining while revenue still looks fine is a common early-warning pattern boards are trained to watch for, since revenue often lags underlying usage health by a quarter or more
Consistency matters more than perfection here — showing the same metric, defined the same way, update after update, builds far more investor trust than switching definitions to make the number look better in any given quarter

Example

A ride-sharing app picks “weekly completed rides” as its North Star Metric, since it reflects real usage better than app downloads or signups — a rider who downloads the app but never completes a ride hasn’t actually experienced the product’s value. The company then breaks that number down into an input tree: rider signups, first-ride conversion rate, rides per active rider per week, and driver availability in each city. Each team owns one branch of that tree — marketing owns signups, the onboarding team owns first-ride conversion, the operations team owns driver supply — while the executive team tracks the aggregate weekly completed rides number every Monday morning.

When the number dips in a specific city, the North Star framework makes it immediately clear which input to investigate first, rather than triggering a scramble across a dozen unrelated dashboards. To guard against chasing ride volume at the expense of quality, the team also tracks average driver rating as a guardrail metric, so a push to increase rides never quietly comes at the cost of service — and six months in, weekly completed rides has become the number every team, from engineering to marketing, references by default when deciding what to work on next.

The payoff shows up clearly at the next board meeting: instead of presenting a dozen loosely related charts, the CEO opens with a single slide showing weekly completed rides trending up 18% quarter over quarter, followed by the input-tree breakdown showing that the gain came primarily from improved first-ride conversion in three newly launched cities. A board member asks whether growth came at the expense of driver satisfaction, and the guardrail metric answers the question in a single glance — driver ratings held steady over the same period, meaning the growth was real rather than borrowed against future service quality.

Referenced by

Dig deeper

Spot an error in this note?