North Star Metric Workshop

Purpose

The North Star Metric Workshop aligns the product team around one metric that best captures the core value the product delivers to customers. By identifying the North Star and its input metrics, the team gains focus and can prioritize work that moves the needle.

At a glance

How to run

1. Define the game (15 min) — What type of product is this? Attention (time spent), Transaction (purchases), Productivity (tasks completed)? This frames the North Star.
2. Brainstorm candidates (15 min) — Each person proposes 1–3 candidate North Star metrics. Write them on cards.
3. Evaluate candidates (20 min) — For each candidate, test: Does it measure value delivered to customers? Is it measurable? Does it correlate with revenue? Is it actionable by the product team?
4. Select the North Star (10 min) — Vote or consensus-decide on one metric.
5. Map input metrics (20 min) — What levers drive the North Star? Identify 3–5 input metrics (e.g., for "Weekly active teams," inputs might be: new sign-ups, activation rate, retention rate, team invites).
6. Set targets (10 min) — Define current baselines and targets for the North Star and each input metric.

Materials needed

• Product usage data and analytics
• Metric candidate cards
• North Star framework diagram (North Star + inputs)
• Shared document for capturing decisions

Pitfalls & common mistakes

• North Star is a revenue metric — Revenue is a lagging indicator. The North Star should measure customer value, which then drives revenue.
• Too many metrics — One North Star, not three. Focus is the point.
• Not actionable — If the product team cannot influence the metric, it is the wrong one.
• Set and forget — Review the North Star quarterly. As the product evolves, the metric may need updating.

Inclusion & accessibility

• Share product analytics and candidate metrics in advance.
• Ensure non-technical team members understand each candidate metric.
• Use silent brainstorming before group discussion.

Variations

• North Star + OKR alignment — Set OKRs around the North Star and its inputs.
• North Star audit — Review the current North Star against recent product changes.
• Metric tree — Expand the input metrics into a full tree showing how each is influenced.

When NOT to use this

• For internal tools with a captive audience where metrics are less relevant.
• If the product is pre-launch with no usage data — define the North Star hypothesis and validate after launch.

Source & further reading

• Cutler, J. (2020). "The North Star Framework." amplitude.com
• Croll, A. & Yoskovitz, B. (2013). *Lean Analytics*. O'Reilly.