Agree the subject, boundary and decision before filling the model.
North Star Metric
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
Prerequisite
What needs to be finished first
Bring source material and people who know the work; distinguish facts from assumptions.
Preparation
What needs to be ready before start
Shared visual workspace, source evidence, and an agreed decision question.
Product, analytics, customer research, engineering/data, decision owner.
Collect existing data, examples, constraints and relevant stakeholder perspectives.
2–4 h for a working session plus data validation with analytics owners.
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.
Core question
The one question this method answers
Which single metric best captures recurring customer value?
Flow
Phases with goal, actions, output and pitfall
Connects customer value to a leading product metric, its input metrics and guardrails.
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.
- 1
User value
Describe delivered user value

Goal
Value statement
Inputs for this step
- Product vision, user research and use context
Actions
- State the repeatable value users should receive, independent of revenue or internal delivery activity.
Output
Value statement
Value statement
Quality check
Would the metric reflect an actual user success?
Pitfall
More page views are assumed to equal user value. Name a completed user task or received benefit.
Timing: Allow time according to scope and evidence; no universal duration.
- 2
Candidates
Propose and test metric candidates

Goal
Justified NSM candidates
Inputs for this step
- Events, user value and long-term business outcomes
Actions
- Test candidates for user value, team influence and a leading relationship to sustainable business results.
Output
Justified NSM candidates
Justified NSM candidates
Quality check
Is it understandable, influenceable and leading?
Pitfall
Revenue or activity measures short-term performance only. Choose a value metric and keep business measures as guardrails.
Timing: Allow time according to scope and evidence; no universal duration.
- 3
Drivers
Derive inputs and guardrails

Goal
Driver model and guardrails
Inputs for this step
- Candidate metric, behaviour and quality risks
Actions
- Derive a few observable drivers and add measures that reveal unwanted side effects.
Output
Driver model and guardrails
Driver model and guardrails
Quality check
Are inputs plausibly causal rather than merely correlated?
Pitfall
Too many inputs dilute focus or invite gaming. Keep measurable drivers with a plausible connection.
Timing: Allow time according to scope and evidence; no universal duration.
- 4
Measure
Specify measurement and review

Goal
Metric specification and review
Inputs for this step
- Event names, cohorts, windows and data owner
Actions
- Specify numerator, denominator, period, exclusions, segments and owner; define review triggers when product changes.
Output
Metric specification and review
Metric specification and review
Quality check
Could two analysts calculate the same value?
Pitfall
Inconsistent events break the time series. Test with real events and version definition changes.
Timing: Allow time according to scope and evidence; no universal duration.
Artifact
What comes out at the end
Sketch: what the artifact looks like
Connects customer value to a leading product metric, its input metrics and guardrails. Record scope, evidence, assumptions, owner and next review in the versioned artifact.
Record scope, date, participants, source version and owner. Note changed assumptions and the reason for each revision.
- Shared whiteboard or paper template
- Source links, records or measurement data
strategy-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-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
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
north-star-metric-beispiel.md
Concrete filled scenario, fictional 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.
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Describe delivered user valueMore page views are assumed to equal user value.View in phase
- Propose and test metric candidatesRevenue or activity measures short-term performance only.View in phase
- Derive inputs and guardrailsToo many inputs dilute focus or invite gaming.View in phase
- Specify measurement and reviewInconsistent events break the time series.View in phase
Describe delivered user value
More page views are assumed to equal user value.
Name a completed user task or received benefit.
Propose and test metric candidates
Revenue or activity measures short-term performance only.
Choose a value metric and keep business measures as guardrails.
Derive inputs and guardrails
Too many inputs dilute focus or invite gaming.
Keep measurable drivers with a plausible connection.
Specify measurement and review
Inconsistent events break the time series.
Test with real events and version definition changes.
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

