Define and validate your product's North Star metric

One Metric to Rule Them All: The Case for a North Star

When everyone on a product team optimizes for their own metric, the product pulls in five directions at once. Growth wants more signups. Engagement wants more sessions. Revenue wants higher ARPU. The result is a fragmented roadmap and constant prioritization fights. According to Amplitude's 2024 Product Report, teams that align around a single North Star metric ship 30% more impactful features and have 20% higher team satisfaction scores compared to teams tracking multiple competing KPIs.

What Makes a Good North Star

Not every important metric qualifies as a North Star. Revenue is a lagging indicator — by the time it moves, the cause happened weeks ago. DAU is too shallow — it measures presence, not value delivery. The ideal North Star sits at the intersection of customer value and business growth: it captures the core action that, when it happens more often, means both customers and the business are winning.

Spotify uses "time spent listening." Airbnb uses "nights booked." Slack used "messages sent within teams." Each of these metrics directly reflects user value delivery and predicts future revenue. The key test: if this metric goes up, is it almost certainly good for both customers and the business?

How the North Star Metric Prompt Works

This prompt guides you through four phases. First, it applies five criteria to filter out vanity metrics and lagging indicators. Then it generates multiple candidates and scores them systematically — preventing the common trap of anchoring on the CEO's favorite number. A validation phase tests the top candidate against historical data, perverse incentives, and comprehension. Finally, an operationalization step turns the metric from a concept into a daily reality with targets, input metrics, dashboards, and review cadences.

The decomposability check in Step 3 is particularly important. A North Star metric that can't be broken into input metrics that individual teams own becomes a spectator sport — everyone watches it, no one moves it.

When to Use It

• Your product team tracks more than 5 "key" metrics and debates which one to optimize
• You're setting annual goals and need a unifying metric across product, growth, and business teams
• A leadership change has created confusion about what success looks like
• Your current North Star hasn't been revisited in 12+ months and the product has evolved significantly
• You're scaling from one team to multiple squads and need a shared success measure

Common Pitfalls

Choosing a metric you can't move. If your product team can't influence the metric through their work, it's a business outcome, not a product North Star. Pick something closer to the product experience.

Setting it and forgetting it. Products evolve. A metric that was perfect at seed stage may be wrong at Series C. Revisit your North Star annually and adjust if the product's value proposition has shifted.

Conflating input metrics with the North Star. "Number of features shipped" or "sprint velocity" are input metrics — they measure team activity, not customer value. The North Star should always reflect something the customer experiences.

Sources

• North Star Playbook — Amplitude's guide to finding and operationalizing your North Star
• What is a North Star Metric? — Future (a16z) on choosing the right metric for your business model
• Teams Aligned Around a North Star Ship 30% More Impactful Features — Amplitude's 2024 research on metric-aligned teams