What is the difference between OKRs and KPIs?
KPIs are the numbers you watch continuously to know whether the business is healthy. OKRs are the ambitious, time-boxed changes you commit to this quarter. A KPI can run flat forever and still be doing its job; an OKR that doesn't move has failed. Most confusion comes from writing KPIs and calling them OKRs.
The practical difference
A KPI is a thermometer. Monthly active users, gross margin, p95 latency, support ticket volume — you watch them permanently, and a flat line is often good news.
An OKR is a destination. An Objective states what changes and why it matters; Key Results state how you'll know it happened. It exists for one quarter and then it's over.
The test: if the number would still be worth reporting when nobody is actively working on it, it's a KPI.
Why the confusion is expensive
The most common failure is converting the whole KPI dashboard into OKRs. Twelve metrics become twelve objectives, every team owns a number, and the quarter is spent nudging things that were already fine. The framework's entire value — forcing a choice about what actually changes — is thrown away in the setup.
The second failure is the opposite: objectives so aspirational they can't be evidenced. "Delight our customers" is not an objective, because no key result honestly attaches to it.
What good looks like
Satya Nadella's cloud-first turnaround at Microsoft is a useful illustration of scale. The objective was a genuine change of direction, and the key results were unambiguous and countable — Azure revenue, commercial cloud run rate — not "improve cloud perception". People could tell whether it was working.
Amazon's working-backwards method solves the same problem from the other end: writing the press release first forces you to state the outcome in a way that can later be checked. Whatever the framework, the discipline is identical — commit to a number that can embarrass you.
Seen in practice
Case studies where this shows up as a real decision, not a definition.
Related questions
Can a KPI be a key result?
Yes, and this is the normal relationship. A key result is usually a target movement in an existing KPI — 'reduce p95 load time from 4.1s to 2.0s' takes a metric you already monitor and commits to changing it this quarter.
How many OKRs should a team have?
Three objectives with three key results each is the common ceiling, and most teams should be closer to one or two objectives. The point of the framework is forced prioritisation; a list of nine objectives is the thing OKRs were invented to prevent.
Should OKRs be tied to performance reviews?
Generally no. OKRs are meant to be ambitious enough that hitting 70% is a good outcome, and tying them to compensation reliably produces conservative targets that everyone hits — which destroys the signal the framework exists to create.
More on metrics
Last reviewed 2026-09-07