There are a hundred product management KPIs you could track and maybe five you should. The job isn't measuring everything — it's picking the handful that tell you whether the strategy is working, and ignoring the vanity numbers that only go up. This page covers the metrics frameworks PMs actually use — North Star, AARRR, the SaaS pyramid, leading vs lagging — what each one measures, and how to choose the few that fit your product. Then the honest part: a metric encodes a bet about what to optimize, and when the strategy changes, the metrics should too.
The trap is the vanity metric — a number that reliably goes up (total registered users, page views, cumulative downloads) and tells you nothing about whether the product is working. A good KPI for a product manager is one a decision hangs on: if it moved, you'd do something differently. If no decision changes regardless of the number, you're measuring for comfort, not for steering.
The other split worth knowing is leading vs lagging. Lagging metrics (revenue, churn) tell you what already happened; leading metrics (activation rate, weekly active usage) move first and predict the lagging ones. You steer with leading indicators and judge with lagging ones — a dashboard of only lagging metrics is a rear-view mirror.
A few frameworks structure the chaos. Pick one as your backbone — usually a North Star plus a small tree of inputs — rather than tracking all of them at once.
The single metric that best captures the value your product delivers — nights booked, messages sent, weekly active teams. Everything else is an input to it. Its power is focus; its danger is picking one that rewards the wrong behavior, so choose it as carefully as a strategy.
Acquisition, Activation, Retention, Referral, Revenue — the lifecycle a user moves through. Best for diagnosing where you leak: a great acquisition number with weak activation tells you exactly which stage to fix before pouring in more traffic.
Activation (did a new user reach first value) and retention (do they keep coming back) are the two that predict everything downstream. Most early products do not have a growth problem; they have a retention problem wearing a growth costume.
MRR/ARR, churn, LTV, CAC, payback period — the financial health of a subscription business. These are mostly lagging; they judge whether the product and GTM are working, but you steer with the leading product metrics above them.
Happiness, Engagement, Adoption, Retention, Task success — Google's framework for measuring experience quality, not just usage. Useful when the question is "is this good," not just "are people using it."
The metrics you pick are downstream of your product strategy — they measure whether the bets are paying off.
Choosing a North Star and its input tree is a strategic decision — you're declaring what "working" means. When the strategy shifts, that declaration is out of date, and a team optimizing the old North Star is now rowing hard in the wrong direction. Draftlize keeps the metric tied to the strategy it serves.
In Draftlize your North Star and its inputs are cards linked to the strategic bet they exist to track. The metric isn't a number on a dashboard divorced from why you chose it — it points at the decision that made it the right thing to optimize.
Reposition from self-serve to enterprise and "weekly active users" may stop being the right North Star. Because the metric links to the strategy, it auto-flags stale when the strategy moves — so you re-pick what to optimize deliberately, instead of steering by a number that quietly stopped mapping to the goal.
Everyone — and the AI agents helping with analysis over MCP — reads the live metric definitions and their rationale, so a quarter-old North Star doesn't keep driving roadmap decisions after the strategy that justified it has moved on.
A vanity metric goes up no matter what. A real KPI is one a decision hangs on — and one that should change when the strategy under it does.Track the few that matter. Tie each to the strategy it's supposed to measure.
There is no universal list — it depends on your product and stage. But activation and retention predict almost everything downstream, a North Star metric focuses the team, and for a SaaS business MRR, churn, LTV, and CAC judge financial health. Pick a small set tied to your strategy rather than tracking everything.
The single metric that best captures the core value your product delivers to users — the one number the whole team optimizes, with everything else treated as an input to it. Its strength is focus; the risk is choosing one that rewards the wrong behavior, so it should be chosen as carefully as a strategy.
Lagging indicators (revenue, churn) measure what already happened; leading indicators (activation rate, weekly active usage) move first and predict the lagging ones. You steer with leading indicators and judge results with lagging ones.
A number that reliably goes up and looks good but does not inform any decision — total registered users, cumulative downloads, raw page views. The test of a real KPI is whether a change in it would make you act differently; if not, it is vanity.
Measure with whatever analytics stack you like. Keep the North Star and its rationale in Draftlize, linked to the strategy it serves — so when the strategy moves, the metric flags stale instead of steering the team by a target that no longer maps to the goal.
Start free with $5