Skip to content

North Star Metric

beta  ·  Family strategy-docs  ·  Phase undefined  ·  Sizes lean, full  ·  ~3,850 tokens

The document that names the one metric showing customers get the value the strategy promises, says why that metric, and names the input metrics a team can move. Not the vision’s north star statement; the formula and targets belong to kpi-dashboard.

An operator card. Read it before you fill the template and again before you agree the definition. The reasoning behind every rule here lives in north-star-metrics_companion.md.

Before you start: is this the right document at all?

Section titled “Before you start: is this the right document at all?”

A North Star Metric names the single measure of customer value that shows a product’s strategy is working, and the small set of inputs a team can actually move to drive it. If your real question is something else, write something else.

If the real question is Write this instead
Where are we trying to get to, over years, and why is it worth getting to? product-vision
Which problems will we solve to get there, and which will we not? product-strategy
In what order will we work on those problems? product-roadmap
What measurable change do we expect this period, and did we get it? okrs
What is the formula, the data source, the refresh schedule, or the target behind this number? kpi-dashboard
What does the whole hierarchy of metrics beneath this one look like? the catalog’s own metric-tree document type, which the companion notes is not yet built in this library

Write nothing at all if you cannot yet name a product strategy for this product. A North Star measures whether a strategy is moving the product toward its vision; with no strategy stated, there is nothing for the number to measure yet, and the document would be guessing at both ends.

lean carries the metric’s name and definition, the case for it, its inputs, what it serves, and the trigger that would bring you back to it. That is enough for a first definition, or for a team that is unlikely to be asked what was rejected.

full adds four sections: Candidates Considered, Guardrails, What It Does Not Tell Us, and Definition History. Reach for full once the North Star has already faced, or will soon face, real scrutiny: named alternatives were seriously compared, a stakeholder will ask “why not X”, or the definition has already changed once and the change needs a record.

Guardrails is worth a separate word. It is the one full-only section whose evidence does not come from Amplitude, the publisher this document type is admitted on. Amplitude’s own two documents never use “guardrail” for a measure tracked beside the North Star; the section instead rests on three other sources. Choosing lean and leaving Guardrails out is not skipping an Amplitude step.

Could your team move this number directly? John Cutler, co-author of Amplitude’s own playbook, states the test plainly: “If you can move your North Star directly, it’s probably not a good North Star.” A number your team can push on its own is a lever, not a North Star; the North Star is what the levers are supposed to move.

One boundary check sits beside it, about discipline rather than form: does anything here belong to kpi-dashboard instead? A formula, a data source, a refresh schedule, a target, a threshold. If you catch yourself writing one of those into this document, stop and open kpi-dashboard.

Score each 0, 1 or 2. Below 15 out of 22, the document has named a metric without doing the one thing a North Star is for: letting someone else ask, of a real piece of work, “does this move the north star”, and get an answer instead of a shrug. The lean variant scores against fewer rows; see the scope table below.

# Criterion 0 1 2
1 Counts a real behavior, not a lever No behavior is named, the sentence names an aspiration rather than something that happens, or one team could push the number up directly without any input moving first A behavior is named, but the actor, the window, or both are missing, or a calculation or data source has crept in You can read the sentence once and say back who does what, how often, with nothing in it that belongs in a formula, and no single team can move it except by moving an input
2 Validation is honest The claim that this metric predicts retention or revenue rests on nothing: no evidence, no plan to get any Evidence is named, but it is another product’s data, or the plan to validate has no date and no owner You can point to a correlation run against this product’s own data, or to a dated, owned plan to run one
3 Fits in one sentence The definition takes more than one sentence, or leans on a term only the people who wrote it would recognize One sentence, but it would need an example or a follow-up question before an outsider could use it One sentence, plain enough that you can picture someone in sales or support repeating it back correctly, unprompted
4 Inputs are real levers A row names a team with no measure, or restates the North Star itself under another label Every row names a measure and an owner, but at least one owner would not actually notice it slip For each row, you can name who would notice it slip this week and say in one sentence why moving it should move the North Star
5 Measures, not mirrors The section could be lifted straight out of the product strategy with no change It names the strategy and the vision, but the business outcome is vague, or written as if the metric were that outcome You can say which strategy this number tests, and name the outcome it predicts without being that outcome
6 Trigger, not a date The answer is a calendar entry, with nobody named to notice anything An event is named, but nobody is named as responsible for noticing it A specific shift is named, a specific person owns watching for it, and it is kept distinct from a target the number merely misses
7 Filters a real decision Almost any project in flight could claim to serve this document; nothing here would rule one out The document could rule something out in principle, but nobody has actually tried asking it of a real, named project You can name a real project and show, from this document alone, whether it moves the North Star or not
8 Candidates were real (full) Every rejected candidate is a straw metric nobody was proposing A real candidate appears, but the reason it lost would equally disqualify the metric that was kept At least one candidate could pass a casual glance, and its rejection names the specific test it failed
9 Guardrails earn their place (full) A guardrail restates the North Star itself, or names a check with no stated harm Each guardrail names a real measure, but for at least one you could not say what its decline would actually mean Each guardrail could fall while the North Star climbs, you can state what that fall would mean, and none is the North Star’s own inverse
10 Owns its blind spots (full) The section claims the metric has no real blind spots A blind spot is named, but nothing elsewhere in the document catches the gap it describes A blind spot is named before the metric ships, and a guardrail or an input exists in this document because of it
11 History survives the change (full) An earlier definition is missing from a North Star that has in fact changed, and there is no “first definition” entry either The new definition is recorded, but the old one, or the reason for the change, is missing The old definition sits beside the new one, dated, with the shift in product, market, or strategy that caused it, or a dated “first definition” entry if there is no earlier one

Which rows apply to what.

Document Rows Maximum Score against
full all 11 22 15
lean 1-7 14 10

Rows 8 to 11 are scored only against full. The lean variant ships no Candidates Considered, Guardrails, What It Does Not Tell Us, or Definition History section, so grading it on those rows would penalise the choice of size rather than the quality of the document.

Nothing here ranks against anything else; read it as a list, not an order.

  • A metric that can only rise. Total registered users, cumulative downloads, and pageviews only go up, and a metric that can never fall cannot warn you when something is wrong. Test it with the doubling question: if this number doubled next month, would the business clearly be healthier? If not, it is a vanity metric wearing a North Star’s clothes.
  • A metric the team can move directly. See the first test above. If your own team’s effort alone can push the number, it is a lever, not the thing the levers are supposed to move.
  • Revenue, or any lagging measure, standing in for the metric. Every source that addresses this agrees on direction: revenue tells you what already happened, not what is about to.
  • Gaming it once it becomes a target. Named independently, under different words, by a reference source asking how to keep the number from being gamed, and by a practitioner’s essay, South Star Metrics, about exactly this failure.
  • Letting departments run their own, uncoordinated North Stars. One practitioner’s own warning is that this compounds as a company grows; nobody is left who can say which number the company is actually steering by.
  • Silently rewriting the definition instead of recording the change. The discipline a glossary entry states directly: preserve the old definition and explain the break in the series rather than rewriting history.
  • A composite score standing in for a single metric. Composite scores with several weighted inputs fail the one-sentence test even when they are, on paper, more complete.
  • Mistaking it for a goal-setting method. Amplitude’s own playbook names this directly as what the Framework is not, and says so right next to the warning that it can still be a foundation goals are built on.
  • You can say the definition back in one sentence, and so could someone outside the team.
  • Nothing in the document is a formula, a data source, a refresh schedule, a target, or a threshold.
  • Every input names an owner who would actually notice it slip.
  • The revisit trigger names an event and a person, never only a date.
  • If this is the full variant: Candidates Considered, Guardrails, What It Does Not Tell Us, and Definition History are filled with real content, not left at “N/A” by default.
  • You have deleted every HTML comment before sharing it.

north-star-metrics_template-lean.md · ~3,850 tokens

---
title: "{{product_name}} North Star Metric"
product: "{{product_name}}"
owner: "{{who_owns_this_metric}}"
status: "{{draft_or_agreed}}"
last_updated: "{{date}}"
doc_type: north-star-metrics
size: lean
source_template: north-star-metrics
source_template_version: 0.1.0
---
<!--
LEAN NORTH STAR METRIC. The shortest form that still names the metric, the case for it, its input
metrics, what it serves, and the signal that would bring you back to it. Use it to settle what your
product's single measure of customer value is and why, before anyone asks what was rejected or what
would change it. To grow it into a form that also names rejected candidates, standing guardrails, the
metric's own blind spots, and a change log, see north-star-metrics_template-full.md. ADD sections
after When We Revisit It; never rename or reorder the five below, because the full variant is a strict
ordered superset of this one.
ADMISSION, AND WHAT IT MEANS FOR THIS TEMPLATE. This type is admitted on one publisher, Amplitude,
across two documents that both reserve all rights. Every field name, section name and layout choice
below is this library's own wording, never Amplitude's worksheet, its checklist text, or its sidebar
heuristic. Where a sentence below is attributed to Amplitude or another source, it is reported as that
source's own words, never offered as this template's own field label.
WHAT A NORTH STAR METRIC IS, AND IS NOT. It names the single measure of customer value that shows a
product's strategy is working, states the case for it, and names the inputs a team can actually move.
It is NOT the product vision (that names the destination; this names the number that shows the
strategy is getting you there). It is NOT the product strategy (that chooses which problems to solve;
in this library's chain, drawn from sources that describe a North Star as measuring the current
strategy, the North Star comes after it; one source orders the two the other way, and
north-star-metrics_companion.md section 6 names both camps). It is NOT OKRs (those reset each period;
a North Star persists and is revisited on a trigger, not a calendar). And it is NOT kpi-dashboard
(that carries the formula, the data source, the refresh schedule, the target and the threshold; this
document carries one definition and the case for choosing it). See north-star-metrics_companion.md
section 8 for the fuller set of boundaries.
WHAT STAYS OUT, AT EVERY SIZE. No formula, no data source, no refresh schedule, no target, no
threshold, no dashboard layout, and no tree of metrics below the inputs. All of that belongs to
kpi-dashboard, except the metric tree, which the catalog lists as its own document type with the North
Star at its top node. If you find yourself writing a calculation here, stop and open kpi-dashboard
instead.
ONE NORTH STAR, PER PRODUCT OR PER PRODUCT LINE. The default is one North Star metric for the whole
product. The named exception is a company with genuinely separate product lines, each with its own
customers and its own profit and loss; that company may need one North Star per line, not one per team
or one per feature. A direct competitor to the admitting publisher disputes the one-metric premise as
"mostly rhetorical"; this bundle follows the one-per-product rule with the product-line exception. See
north-star-metrics_companion.md section 6.
HOW TO FILL THIS IN
1. Read the comment under each heading: WHAT it wants, WHY it matters (with a pointer into
north-star-metrics_companion.md), guiding questions to ASK, a GOOD and a WEAK example, and the TRAP
to avoid. For the table, PRIORITY explains the ordering rule and ROW HINT says what a good row
contains.
2. Replace each {{placeholder}} with your content. Name no formula, data source, refresh schedule,
target, or threshold anywhere in this document; those belong to kpi-dashboard.
3. If a section does not apply, write "N/A" and one line of why, rather than deleting it.
4. Before you share it: self-grade against north-star-metrics_guide.md, then DELETE every HTML
comment. They are guidance, not content.
-->
# {{product_name}} North Star Metric
## The North Star
<!-- WHAT The metric's name and its definition in one statement: the behavior it counts, who does
it, and over what time window. The product it covers, if your company runs more than one.
WHY Cut the SaaS states the window directly: "Pick a metric that counts that action across a
sensible time window, like weekly." Ballpark adds the bar for the definition itself:
"Prefer a definition people can explain, inspect and reproduce." Amplitude's own fill-in
exercise, reported here and not reproduced as this template's own field, asks for the
metric's name and a one-sentence definition; this section asks for the same two things in
the library's own wording. Deep dive: north-star-metrics_companion.md section 3 (The North
Star).
ASK What behavior does this metric count? Who performs it, and over what window, weekly or
some other sensible period? Could someone outside your team read the definition and
reproduce the count themselves? Does your company run more than one product, and if so,
which one does this North Star belong to?
GOOD "Our North Star is weekly closed expense reports: the count of expense reports that reach
Approved or Reimbursed status, per active finance team, each week, with no manual nudge
from a success manager."
(names the behavior, the actor, and the window, and leaves the calculation out)
WEAK "Our North Star is engagement."
(no behavior, no actor, no window; nobody could reproduce a count from this)
TRAP Writing the calculation instead of the definition. A column for exclusions, a query
snippet, or a refresh schedule belongs in kpi-dashboard's Metric Definitions section, not
here. -->
{{north_star_definition}}
- Product this North Star belongs to, if your company has more than one: {{product_scope}}
## Why This Metric
<!-- WHAT The case for this metric over another: the customer value it expresses, why it leads
revenue rather than reporting it, why it is not a vanity metric, and what shows it
predicts retention or revenue in this product's own data.
WHY Amplitude's own checklist asks, among other things, "Does it express customer value?" and
"Is it a leading indicator of success?" A second Amplitude article adds the instruction to
check the claim against your own evidence: "Validate that it predicts retention and
revenue in your own data." Koji states where that evidence has to come from: "You cannot
write this sentence by staring at a dashboard." Deep dive: north-star-metrics_companion.md
section 3 (Why This Metric).
ASK What does this metric say about the value a customer actually gets? Why does it move
before revenue rather than after? Could it rise forever even if the business got no
healthier, the doubling test one source proposes? What shows, in your own data or your own
customer conversations, that this metric predicts retention or revenue, and if nothing
does yet, how will you find out?
GOOD "Closed expense reports measures the moment a finance team gets what it pays us for: an
expense submitted, reviewed and settled without chasing anyone. It is not revenue, which
only tells us the deal closed, not whether the team is getting value every week. We have
not yet run the correlation against renewal; that test is scheduled for next quarter."
(states the value, the leading-versus-lagging case, and labels the missing validation
honestly)
WEAK "This metric matters because it's the number that matters most."
(restates the question; names no customer value, no leading-indicator case, no validation)
TRAP Treating "it predicts revenue" as self-evident. The admitting source's own instruction is
to validate the claim in your own data, not to assume a metric is a leading indicator
because it sounds like one. -->
- The customer value case: {{customer_value_case}}
- Why it leads rather than lags revenue: {{leading_indicator_case}}
- Why it is not a vanity metric: {{not_vanity_metric_case}}
- What shows it predicts retention or revenue in your own data, or how you will find out:
{{validation_evidence}}
## Input Metrics
<!-- WHAT Three to five measures a team can actually move, that combine to drive the North Star,
each with a named owner.
WHY Amplitude defines inputs as "a set of three to five influential, complementary factors
that you believe most directly affect your North Star Metric and that your team can
directly influence through your product." Basedash states the ownership rule: "Each input
is something a specific team can own and affect directly." A reference source goes
further, naming six to ten input metrics across a customer journey with each team owning
one to three of them; this bundle keeps Amplitude's three to five as its default and
reports the larger count as that one source's own. Amplitude's own breadth, depth,
frequency and efficiency heuristic for finding inputs is reported here as one vendor's
own, never prescribed; a competing vendor structures inputs as a hierarchy instead, and
this bundle prescribes neither. Deep dive: north-star-metrics_companion.md section 3
(Input Metrics), section 6 (How input metrics are organized).
ASK What three to five measures, if your team moved them, would move the North Star? Who owns
each one, specifically enough that they would notice it slipping? Could the North Star
move without any of these moving, in which case is something missing? Is any row really
the North Star itself, counted a different way?
PRIORITY Three to five is this bundle's default. One reference source allows six to ten across
a longer customer journey, with one to three per team. Past five rows, every one still
needs an owner who can actually move it, or it has not earned its place.
ROW HINT A good row names one measurable behavior, one owning team, and why moving that
behavior should move the North Star. A weak row names a team with no measure, or restates
the North Star's own definition under a different label.
GOOD | Receipt-capture completion rate | Mobile team | A report cannot close until its
receipts are attached; this is the most common place a report stalls |
WEAK | Customer happiness | Everyone | |
TRAP Adding a row because a team wants one, not because moving it would move the North Star. A
row with no real lever behind it is the same failure Amplitude's own playbook names for
the North Star itself: insisting on more than real boundaries support. -->
| Input Metric | Owning Team | Why It Drives the North Star |
|---|---|---|
| {{input_metric_name}} | {{input_metric_owner}} | {{input_metric_rationale}} |
## What It Serves
<!-- WHAT The product strategy this metric measures, the vision that strategy serves, and the
business outcome this metric is expected to predict.
WHY Amplitude names one part of a good North Star as "a metric that serves as a key measure
of your current product strategy." This library places the North Star after the strategy
it measures; one practitioner orders the two the other way, putting the North Star first.
Both camps are named in north-star-metrics_companion.md section 6 (The chain position is
contested); this section states this library's position and asks you to name your
strategy, not to settle the debate. Deep dive: north-star-metrics_companion.md section 3
(What It Serves).
ASK Which product strategy does this number show is working? How does that strategy serve the
product vision? What business outcome, revenue, retention, or expansion, is this metric
expected to predict, and does it correlate with that outcome without being that outcome?
GOOD "Closed expense reports measures whether our strategy, becoming the system finance teams
trust enough to stop keeping a shadow spreadsheet, is working. It serves the vision of a
finance team that never reconciles a paper receipt by hand. It is expected to predict
renewal, not replace it as the renewal number itself."
WEAK "This metric supports our overall goals."
(names no strategy, no vision, no outcome)
TRAP Copying the strategy's own language in here unexamined. If this section could be lifted
straight out of the strategy document with no change, ask whether the metric actually
measures the strategy or is simply repeating it. -->
- The product strategy this metric measures: {{strategy_it_measures}}
- The product vision that strategy serves: {{vision_it_serves}}
- The business outcome it is expected to predict, and how it differs from that outcome:
{{business_outcome_expected}}
## When We Revisit It
<!-- WHAT The signal that would bring the team back to this definition, not a calendar date.
WHY Amplitude's own playbook asks, "What will be your signal to revisit this metric?" A
reference source states the trigger from the other side: "Only change the NSM when
strategy or product fundamentally shifts." Spotify's experimentation glossary names the
stakes: "Changing the north star is a significant organizational decision." Sources
disagree sharply on cadence, by stage, by a flat yearly rule, or on a fixed quarterly
calendar; this section asks for the trigger because no source read agrees on a number. Deep
dive: north-star-metrics_companion.md section 3 (When We Revisit It), section 6 (How often
it changes).
ASK What change in the product, the market, or the strategy would make you look at this
definition again? Who notices that signal first? What would have to be true for the
metric itself, not just its target, to change?
GOOD "We revisit this definition if we start selling to teams that approve travel budgets
rather than individual expense reports; closed expense reports would no longer describe
the value those teams get. The head of product owns watching for that shift."
WEAK "We'll review this every quarter."
(a calendar entry, naming no event and nobody responsible for noticing one)
TRAP Confusing a trigger with a target miss. A quarter where the number does not move is a
signal to investigate the input metrics, not, on its own, a reason to redefine the North
Star itself. -->
- The signal that would bring you back to this definition, not a date: {{revisit_trigger}}
- Who is responsible for noticing that signal: {{revisit_owner}}

The reasoning, the history and every source, in the repository:

  • Companion - the long-form argument: why these sections, where the sources disagree, and what the bundle refuses to claim
  • History - what changed in this bundle, and when
  • Research log - every source consulted, with what each one actually supports
  • Catalog metadata - the machine-readable record this page is generated from

Catalog record: 9 sections across 1 format(s).