North star metric: what it is and how to find yours

The concept emerged from the growth teams at Silicon Valley technology companies in the early 2010s, but the underlying principle is far older. Peter Drucker argued decades ago that what gets measured gets managed. The North Star metric takes that idea to its logical conclusion: if you could only measure one thing, what would it be? The answer should capture the moment your product delivers real value to a real person. Not revenue in isolation, not vanity metrics like page views, but a measure that reflects genuine value exchange between your business and your customers.

What makes the North Star metric distinct from other high-level KPIs is its dual nature. It must reflect customer value and business value simultaneously. Revenue alone fails this test because a company can grow revenue through aggressive pricing while destroying customer goodwill. Monthly active users alone fails because users can be active without deriving meaningful value. The best North Star metrics sit at the intersection: they grow when customers get what they came for, and that growth translates directly into sustainable business performance.

This is not an academic exercise. Organisations that rally around a well-chosen North Star metric make faster decisions because every trade-off has a common reference point. Should we invest in acquisition or retention? Which will move the North Star more? Should we build feature A or feature B? Which one has a stronger causal path to the metric that matters? The North Star does not answer these questions automatically, but it provides the framework within which answers become clearer.

Most organisations suffer from metric sprawl. Every team tracks its own numbers, every dashboard tells a different story, and every quarterly review turns into a debate about which metric matters most. The result is not data-driven decision making. It is data-drowned paralysis. A North Star metric cuts through this by establishing a single source of strategic truth that everyone, from the board to individual contributors, can orient around.

Choosing the right North Star metric is one of the highest-leverage decisions a leadership team can make. Get it right, and it aligns hundreds of smaller decisions for years. Get it wrong, and you build an organisation that is optimising for the wrong thing. The criteria below will help you evaluate candidates and land on a metric that actually serves as a reliable compass.

1. 1

   It reflects value delivered to customers

   The metric should grow when customers genuinely benefit from your product or service. This is the most important criterion and the one most often violated. Revenue reflects value captured by the business, but it does not guarantee value delivered. A metric like "weekly active projects" or "messages sent" is closer to the moment of value delivery because it measures the customer actually using and benefiting from what you built.

2. 2

   It correlates with long-term revenue

   Customer value and business value must be linked. If your North Star goes up but revenue stays flat, you are measuring the wrong thing. Test this empirically: do cohorts with higher values of the metric retain longer, expand more, and generate more lifetime value? If the answer is yes, the correlation holds. If it does not, keep looking.

3. 3

   Multiple teams can influence it

   A North Star metric that only one team can move is just a team-level KPI with a grander name. The whole point is cross-functional alignment. Marketing should be able to influence it through acquisition quality. Product should be able to influence it through activation and engagement. Support should be able to influence it through retention. If it only lives in one department, it cannot serve as the organising principle for the business.

4. 4

   It is measurable on a regular cadence

   You need to be able to track it weekly, at minimum. Annual metrics like lifetime value are important for validation, but they are too slow for operational decisions. Choose something you can observe frequently enough to act on. If the metric only updates quarterly, you will not catch problems until it is too late to respond.

5. 5

   It is simple enough to explain in one sentence

   If you cannot explain the metric to a new hire in under thirty seconds, it is too complex to serve as a North Star. The metric needs to be understood intuitively by everyone in the organisation, not just the data team. Composite indices and weighted scores fail this test. "Weekly active teams" passes it. Simplicity is not a nice-to-have. It is a requirement for adoption.

One useful exercise is to list your top five candidate metrics and score each one against these criteria on a scale of one to five. The metric with the highest total score is usually the right choice, though judgement still matters. If two candidates score similarly, lean toward the one that is easier to decompose into drivers, because the real power of a North Star metric comes not from the number itself but from understanding the system of inputs that cause it to move.

The right North Star metric depends heavily on your business model. A SaaS company and a marketplace create value in fundamentally different ways, so the metric that captures that value creation will be different too. The table below shows common patterns, but treat these as starting points, not prescriptions. Your specific context, stage, and competitive dynamics should shape the final choice.

Notice that none of these examples are pure revenue metrics. That is deliberate. Revenue is a lagging indicator of value delivery. By the time revenue declines, the underlying problem, whether it is engagement, activation, or retention, has been building for weeks or months. A good North Star metric sits upstream of revenue, close enough to the customer experience that it moves before the financial impact materialises.

B2B SaaS companies face a particularly interesting choice. ARR is the metric the board cares about, and for good reason. But ARR on its own does not tell you whether customers are deriving value. A company can grow ARR through aggressive sales while customer engagement deteriorates. That is why many mature SaaS organisations use a usage-based North Star, such as weekly active teams or features adopted per account, as the leading indicator and track ARR as the lagging financial confirmation.

For marketplaces, GMV works because it reflects the health of both sides simultaneously. If sellers are not listing, GMV drops. If buyers are not purchasing, GMV drops. It is a natural barometer of marketplace vitality. The challenge is that GMV can be inflated by a small number of high-value transactions, so many marketplaces pair it with transaction count or active buyer-seller pairs as secondary checks.

Choosing a North Star metric seems straightforward in theory. In practice, organisations consistently fall into the same traps. Recognising these patterns before you commit to a metric can save months of misaligned effort.

Here is the uncomfortable truth about North Star metrics: knowing the number is not the same as knowing what to do about it. Suppose your North Star is weekly active teams, and last week it dropped by 8%. What do you do? The metric itself gives you no guidance. Is it an acquisition problem? An activation problem? A retention problem? A product quality issue? A seasonal pattern? The North Star tells you something is wrong. It does not tell you where to look.

This is where most organisations stall. They choose a North Star metric, celebrate the alignment it creates, and then discover that a single number is too abstract to drive daily decisions. The marketing team does not know how their campaigns connect to it. The engineering team does not know which bugs to prioritise. The support team does not know whether their response time improvements actually matter. Everyone is aligned on the destination, but nobody has a map.

The solution is decomposition. A North Star metric needs to be broken down into the drivers, sub-drivers, and operational inputs that cause it to move. This decomposition creates a metric tree, a hierarchical model where every metric is connected to the ones above and below it through causal relationships. The North Star sits at the root. Beneath it, each branch represents a different pathway through which teams create value.

In the tree above, revenue decomposes into three drivers: new customers, average revenue per customer, and retention rate. Each of those decomposes further into the specific inputs that teams can influence. A marketing manager can see exactly how organic traffic and paid traffic feed into website visitors, which feed into new customers, which feed into revenue. An engineer working on onboarding can trace how trial-to-paid conversion connects to new customer acquisition. A support lead can see how their satisfaction scores influence retention.

This is the critical shift. A metric tree turns a single number into a system of actionable levers. Without it, the North Star is a motivational poster. With it, the North Star becomes a navigable model where every person can see their contribution to the outcome that matters.

Decomposition also reveals leverage. Not all inputs have equal impact on the North Star. When you map the full tree and connect it to real data, you can measure the correlation strength of each relationship. You might discover that improving trial-to-paid conversion by 10% has twice the impact on revenue as increasing website traffic by 10%. That insight changes how you allocate resources, where you focus engineering effort, and which experiments you prioritise. Without the tree, these leverage points remain hidden inside aggregate numbers.

The practical implication is straightforward: do not stop at choosing a North Star metric. The real work begins when you ask "what causes this to move?" and keep asking until you reach the operational inputs your teams control every day. That chain of cause and effect, from North Star to daily levers, is the metric tree. It is what turns strategy into execution.

The concept of the One Metric That Matters (OMTM) was popularised by Alistair Croll and Benjamin Yoskovitz in "Lean Analytics." It is often used interchangeably with the North Star metric, but the two concepts serve different purposes and operate at different time horizons.

The OMTM is stage-specific. It changes as your company moves through different phases of growth. A pre-product-market-fit startup might focus on activation rate. A company scaling acquisition might focus on cost per acquisition. A mature business optimising profitability might focus on gross margin. The OMTM is the metric that matters most right now, given where the business is today.

The North Star metric, by contrast, is meant to be durable. It represents the fundamental value your business creates and should remain stable for twelve months or longer. It does not change when your focus shifts from acquisition to retention, because both acquisition and retention are inputs that feed into it.

The relationship between the two is hierarchical. Your North Star metric sits at the top of your metric tree. Your OMTM is the specific branch of that tree where you are focusing effort right now. The North Star provides the enduring compass. The OMTM provides the current marching orders. An organisation might keep "weekly active teams" as its North Star for three years while shifting its OMTM from activation to engagement to expansion as each becomes the binding constraint.

This distinction matters because it resolves a common tension. Teams often struggle with the instruction to have "one metric that matters" when their focus naturally shifts over time. The answer is that both concepts are valid, but they operate at different levels. The North Star is the metric that always matters. The OMTM is the metric that matters most this quarter. When you have both, strategy and execution stay connected without creating the rigidity that comes from treating a single metric as sacred regardless of context.