Purpose
When product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible.
Growth Planning tool
North Star Metric
Connects customer value to a leading product metric, its input metrics and guardrails.
Connects customer value to a leading product metric, its input metrics and guardrails.
Which single metric best captures recurring customer value?
- Participants
- 3-8
- Time
- 1-2 h
The steps are a practical sequence; adapt them to the method’s purpose and available evidence.
User value
Describe delivered user value
State the repeatable value users should receive, independent of revenue or internal delivery activity.
Candidates
Propose and test metric candidates
Test candidates for user value, team influence and a leading relationship to sustainable business results.
Drivers
Derive inputs and guardrails
Derive a few observable drivers and add measures that reveal unwanted side effects.
Measure
Specify measurement and review
Specify numerator, denominator, period, exclusions, segments and owner; define review triggers when product changes.
Revisit the model when evidence, context or outcomes change. Record what changed and why.
A good fit when
Use it when: Growth Strategy, Cross-functional Alignment. The group can provide the evidence and authority the method requires.
Ideal for
- Growth strategy
- Cross-functional alignment
- Metric clarity
Not good for
- Replacing KPI systems
- Teams without reliable data
Outputs
North Star metric and driver model
User-value metric, plausible input metrics, guardrails and measurement definition.
Metric specification and review
Recorded scope, date, participants, source version, owner, changed assumptions, and the reason for each revision.
North Star driver model
Fictional worked example
Fictional product: North Star Metric = successfully booked appointments attended per week, when both sides confirmed the appointment. Input metrics: bookable slots available, searchers selecting a slot, confirmed bookings. Guardrails: cancellation and no-show rates. Define cohorts, window and exclusions first; more bookings alone do not prove more user value.
| Scenario | Customer value | North Star Metric | Input metrics | Guardrail |
|---|---|---|---|---|
| Metric 1Record an observation or example for this row. | Attended appointment after booking | Confirmed appointments attended / week | Bookable slots; confirmed bookings | No-show rate |
1. Customer value
- Metric 1
- Attended appointment after booking
2. North Star Metric
- Metric 1
- Confirmed appointments attended / week
3. Input metrics
- Metric 1
- Bookable slots; confirmed bookings
4. Guardrail
- Metric 1
- No-show rate
Fictional product: North Star Metric = successfully booked appointments attended per week, when both sides confirmed the appointment. Input metrics: bookable slots available, searchers selecting a slot, confirmed bookings. Guardrails: cancellation and no-show rates. Define cohorts, window and exclusions first; more bookings alone do not prove more user value.
First step
State the repeatable value users should receive, independent of revenue or internal delivery activity.
Good to do first
Deep dive
How it works
A central metric is derived from driving input metrics so effect and cause are considered together. This reveals whether a measure only generates activity or actually shifts real value contribution. The metric serves as a shared focus for prioritization and learning.
In detail
A North Star Metric bundles value creation, usage, and growth into one shared steering signal. It only holds up if the metric is not merely easy to measure but reflects a genuine relationship to value. As a vanity metric it accomplishes little; with matching input metrics, a review rhythm, and clear counter-metrics it becomes real product steering.
Facilitation
Start only once it is clear which customer outcome the product should reliably produce and which usage really counts toward it. Check hard counterexamples against vanity metrics so the metric doesn't just reward activity. The close should include a few input metrics, a review rhythm, and clear rules for course correction.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
In playbooks
Artifact templates
Strategy BriefCompact briefing for strategic context, target state, priorities, and non-goals.markdown
Strategy BriefCompact briefing for strategic context, target state, priorities, and non-goals.
markdownstrategy-brief-markdown.md
Compact briefing for strategic context, target state, priorities, and non-goals.
Strategy Brief
Context
Why is this strategic clarification needed now?
Target state
What should be different in 6-12 months?
Priorities
- ...
- ...
- ...
Non-goals
- ...
Metrics
- North Star Metric:
- Guardrail Metrics:
Risks
- ...
Decisions
Which decisions should follow from this?
North Star Metric: WorksheetPlan definition, ongoing observation and review of the North Star Metric.markdown
North Star Metric: WorksheetPlan definition, ongoing observation and review of the North Star Metric.
markdownnorth-star-metric-working-template.md
Plan definition, ongoing observation and review of the North Star Metric.
North Star Metric: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Metric practice Time: Allow 2–4 hours for definition; data observation and review continue over several weeks and cycles.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Shared visual workspace, source evidence, and an agreed decision question.
- Roles: Product, analytics, customer research, engineering/data, decision owner.
- Advance information: Collect existing data, examples, constraints and relevant stakeholder perspectives.
- Overall time needed: 2–4 h for a working session plus data validation with analytics owners.
- Setup: Describe the durable customer value the product exists to create. Propose metrics that represent that value, not output, activity or revenue alone. Check candidate for user value, influence by product/marketing and leading relationship to business results. Choose a small set of input metrics and guardrails that explain drivers and quality. Specify event definitions, segments, baseline, owner and review/correction cadence.
Prepare for the work steps
User value: Describe delivered user value
- Product vision, user research and use context
Candidates: Propose and test metric candidates
- Events, user value and long-term business outcomes
Drivers: Derive inputs and guardrails
- Candidate metric, behaviour and quality risks
Measure: Specify measurement and review
- Event names, cohorts, windows and data owner
North Star driver model
| Scenario | Customer value | North Star Metric | Input metrics | Guardrail |
|---|---|---|---|---|
| Metric 1 |
- Metric 1: Record an observation or example for this row.
Use product-specific event definitions and include guardrails.
User value: Describe delivered user value
Expected artifact: Value statement
Value statement
Entry:
...
- Would the metric reflect an actual user success?
Candidates: Propose and test metric candidates
Expected artifact: Justified NSM candidates
Justified NSM candidates
Entry:
...
- Is it understandable, influenceable and leading?
Drivers: Derive inputs and guardrails
Expected artifact: Driver model and guardrails
Driver model and guardrails
Entry:
...
- Are inputs plausibly causal rather than merely correlated?
Measure: Specify measurement and review
Expected artifact: Metric specification and review
Metric specification and review
Entry:
...
- Could two analysts calculate the same value?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/north-star-metric/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Product Strategy
KPI Tree
Instead of North Star Metric, when you want to break a target figure down into controllable sub-metrics.
Growth
Flywheel
Maps a recurring growth loop, marks friction points, and derives reinforcing levers.
Growth
Growth Experiment
Connects target group, channel, and hypothesis with a measurement signal, turning campaigns into checkable learning steps.
Growth
Hooked Model
Models trigger, action, variable reward, and investment loops to understand and design repeat usage responsibly.
Engineering
Goal Question Metric
Moves technical problems, hypotheses, and next steps toward a concrete result through "formulate the goal clearly", "derive probing questions for each goal", and "set the review cadence".
Growth
A/B Testing
Tests variants under controlled conditions, keeps the decision log clean, and summarizes results in a learning summary.
Constraints and origin
MediumWorkshop + async1-2 h
Profile
- Method form
- Planning tool
- Participants
- 3-8
- Time
- 1-2 h
- Maturity
- Established
- Origin
- Sean Ellis and growth hacking community
Next up: Pirate Metrics AARRR