Skip to main content
Measurement · Glossary

What Is a North Star Metric? Criteria and Example

A north star metric is a shared measure of the recurring customer value a product creates, used with supporting input, quality, and business-health measures.

In plain language

A north star metric is a single shared measure that represents the recurring value customers receive from a product or service. It helps teams align product and growth work around a durable customer outcome rather than a short-term activity count. A useful north star is measurable, influenced by the team, connected to retention or sustainable growth, and protected by quality and business-health guardrails.

What makes a useful north star metric?

The metric should describe value experienced by the customer, not merely effort produced by the company. Page views, messages sent, leads created, or features shipped can be useful diagnostics, but they become poor north stars when activity can rise without improving the customer's result.

The measure also needs a stable definition. State the qualifying event, eligible customer or account, time window, treatment of repeats, and exclusions. Without those rules, teams may optimise different versions of the same label or improve the number by changing instrumentation rather than the experience.

  • Reflects a meaningful unit of customer value.
  • Occurs often enough to guide decisions before financial reports arrive.
  • Can be influenced by product, service, and growth work.
  • Has a clear calculation and reliable data source.
  • Relates plausibly to retention and sustainable economics.
  • Cannot be improved easily by creating low-quality or unwanted activity.

How do input metrics and guardrails support it?

A north star does not replace a measurement system. Teams need input metrics that explain how the outcome may improve, such as the number of customers who reach an activation milestone, the frequency of a valuable workflow, or the completion rate of an important task. Inputs make the strategy testable because each initiative can state which behavior it expects to change.

Guardrails prevent local optimisation from damaging the business or customer. Depending on the model, they may include retention, customer satisfaction, error rate, refund rate, contribution margin, delivery capacity, or complaint volume. Revenue remains essential, but it may lag the product behavior that creates value and should be interpreted alongside it.

  • Define two to five controllable input metrics for the current strategy.
  • Track at least one quality or trust guardrail.
  • Keep revenue and cost measures visible even when they are not the north star.
  • Segment the measure when different customer groups receive value differently.
  • Review the definition when the product model or customer promise changes.

How should a team choose one?

Describe the recurring progress the priority customer hires the product to make, then list observable moments that demonstrate that progress. Test candidate metrics against real customer behavior and retention rather than selecting the easiest available event. Check whether teams can influence the measure without encouraging harmful shortcuts.

Treat the first version as a documented decision with assumptions and a review date. Compare it with customer interviews, cohort retention, product usage, and commercial outcomes. If the relationship is weak, refine the definition or choose a better representation of value instead of defending the original metric.

Worked example

A north star for a client-expert marketplace

A fictional marketplace initially considers registered members, profile views, and introductions sent. Those counts can grow without a useful engagement. The team chooses “client requirements that reach a mutually accepted expert working session within 30 days” because it combines a stated need, a relevant match, consent from both sides, and a concrete next step. Inputs include complete client briefs, eligible expert coverage, shortlist review time, and acceptance rate. Guardrails include contact-withdrawal rate, session cancellation rate, client satisfaction, expert response burden, and contribution margin. The team reports the count and the share of eligible requirements so growth in volume does not hide a falling success rate.