A North Star Metric is the single metric that best captures the core value a product delivers to customers, and that most directly correlates with the company's long-term revenue success. For SaaS Product Ops, the North Star Metric is the organizing principle around which all product squads align their work and measure their contribution.
?
How do product teams identify the right North Star Metric?
The right North Star Metric sits at the intersection of two criteria: it must reflect genuine customer value delivery (not just a business metric), and it must be a leading indicator of revenue. For Slack, it is "messages sent" — because messages sent reflects team communication happening, and teams communicating renew. For Airbnb, it was "nights booked" — directly reflecting guest value and host revenue. For a SaaS support tool, it might be "tickets resolved per agent per day." The identification process requires analysis of which user behaviors correlate most strongly with long-term retention and account expansion in your own data. Product Ops runs this correlation analysis and facilitates the leadership debate that leads to a single metric being chosen and socialized across the organization.
?
How is the North Star Metric decomposed into input metrics?
The North Star Metric is influenceable only through changes to its input (or lever) metrics. For example, if the North Star is "Weekly Active Users who complete a core action," the inputs are: new user activation rate (how many new users reach that action), retained user engagement rate (how many returning users are still performing it), and churned user recovery rate (win-backs). Product squads own different inputs: the onboarding squad owns activation, the core product squad owns retained engagement. Product Ops builds an input metric tree — a visual model showing how squad-level metrics flow up to the North Star — ensuring every team can see how their sprint work moves the needle.
?
What are the common pitfalls when implementing a North Star Metric?
The most common pitfall is choosing a metric that measures activity rather than value — optimizing for something that looks good without genuinely helping customers. "Users logging in daily" can be gamed by sending push notifications; "Users completing a core workflow action" is far harder to game and more meaningful. Another pitfall is failing to update the North Star as the product evolves — a metric that was right at $1M ARR may misalign incentives at $50M ARR when the customer profile and primary use case have shifted. Product Ops should schedule a formal North Star review annually, rerunning the correlation analysis on current cohort data to confirm the metric is still the best proxy for customer value and revenue growth.
Knowledge Challenge
Mastered North Star Metric? Now try to guess the related 5-letter word!
Type or use keyboard