KPI Frameworks: OKRs, North Stars, and Input Metrics
A practical guide to picking the right framework for each team. OKRs are not KPIs. North stars are not OKRs. Input metrics are what actually move the org.
Why framework confusion kills alignment
Most org-wide metric confusion is not a data problem. It is a framework problem. A team is tracking OKRs, a peer team is tracking KPIs, and the CEO is asking about the north star. The vocabulary collapses and everyone argues about which number is "the real one".
All three frameworks are useful. They are answering different questions. Confusing them is the bug.
OKRs
What they are: A quarterly (or annual) goal contract. An Objective states the qualitative ambition. Three to five Key Results state the measurable outcomes that prove the Objective happened.
When to use them: Planning cycles. New initiatives. Cross-team coordination on a shared goal.
When not to use them: As a replacement for ongoing performance metrics. OKRs expire. Metrics should not.
Common mistake: Treating every metric as an OKR. OKRs are aspirational bets; KPIs are constant measurements. Mixing them erodes both.
KPIs
What they are: Ongoing measurements tied to business outcomes. They do not expire. They are the numbers the team watches every week, quarter after quarter.
When to use them: Operational reporting. Team health checks. Leadership dashboards.
Common mistake: KPI sprawl. Every team adds their favorites until the KPI list has 40 items and no one knows which are critical.
North star metrics
What they are: The single metric that captures the value the product delivers. Every team's work ultimately shows up in the north star.
When to use them: As the headline on every company-wide report. As the denominator for company growth conversations.
Common mistake: Picking revenue as the north star. Revenue is a lagging outcome. The north star should be a leading indicator that correlates with long-term revenue but can move earlier.
Input vs output metrics
Input metrics are actions the team controls directly: calls made, experiments shipped, content published. Output metrics are outcomes the team influences: pipeline generated, MRR added, retention rate. A useful team scorecard has both.
Only holding teams accountable for outputs produces hero behavior or excuse behavior. Input metrics hold teams accountable for the work.
Leading vs lagging
Leading indicators predict future changes in outcomes. Lagging indicators describe what already happened. A healthy report leads with leading indicators and closes with lagging context.
A practical framework: TOP
Pick one from each tier:
- T - Top-level north star. One metric for the whole company. Changes once every 2-3 years.
- O - Outcome KPIs. 5-7 durable outcome metrics. Changes once a year.
- P - Plan OKRs. Quarterly goal set. Changes every quarter.
Reports that follow this structure are legible at every level: exec teams read the TOP, team leads read the O, individual contributors read the P.
Frequently asked questions
What is the difference between OKRs and KPIs?
OKRs are goal-setting: a qualitative Objective paired with measurable Key Results. KPIs are ongoing health metrics: numbers you track regardless of what goal is set. OKRs change every quarter; KPIs are durable.
What is a north star metric?
The single metric that best captures the core value the product delivers to customers. For Airbnb: nights booked. For Slack: messages sent by paid teams. For Donum: reports delivered on time to approved recipients.
How many KPIs should a team track?
Five to nine. Fewer than five and you are missing coverage. More than ten and no one can hold them all in their head, so the framework collapses into the two or three that get attention.
Should input metrics or output metrics be prioritized?
Both, but reported differently. Input metrics go in the weekly team review because the team controls them. Output metrics go in the monthly or quarterly review because the team influences them.