What Is an OKR?
An OKR, short for Objectives and Key Results, is an outcome-focused goal-setting framework: an Objective states what you want to achieve, and one to four Key Results define how you will know you achieved it. All the Key Results must be met for the Objective to count as done.
That two-part shape is deceptively simple, and most of the value is in what it forces you to separate. The Objective is qualitative and human: a clear, time-bound statement of intent a team can rally around. The Key Results are quantitative and unforgiving: from-X-to-Y measures that decide, without argument, whether the intent became reality. Keep them apart and you get ambition you can steer by. Blur them and you get either a poster with no scoreboard or a spreadsheet with no soul.
OKRs are bets, not to-do lists
The single most useful reframe is to read every OKR as a bet: a deliberate commitment of scarce attention to a goal you believe will matter, made in the knowledge that you might be wrong. A to-do list records what you intend to do. A bet records what you believe will happen if you do it, which means it can be tested, graded and learned from. This is why the best OKRs read like hypotheses with numbers attached, and why a quarter spent on a badly-chosen OKR still teaches you something: you learn the bet was wrong, and that is worth knowing.
What OKRs are not
OKRs are not your job description, and they are not a home for everything the team does. The day-to-day work that keeps the business running, reliability targets, support response times, routine throughput, is business-as-usual, and it belongs on a KPI scorecard with thresholds and owners, not inside an OKR. Confusing the two is the most common reason rollouts fail: teams pour their whole operational world into the framework, end up with fifteen "objectives", and focus on none of them. OKRs are reserved for the wildly important, the breakthrough changes that would not happen on their own.
How the pieces fit together
An Objective sets direction; its Key Results prove progress; and the work you actually do to move those Key Results is captured separately as initiatives, process commitments and experiments. Holding the outcome and the work apart is what keeps a team honest: it stops "we shipped the feature" being mistaken for "the metric moved", which is the whole difference between activity and results. Progress is reviewed weekly in check-ins with a confidence score, and the quarter closes with a graded retrospective that asks not just what happened, but what you now believe.
Where OKRs came from
OKRs are less a Silicon Valley invention than an inheritance. They descend from Andy Grove's work at Intel, itself a rebuild of Peter Drucker's Management by Objectives, and were tested in Intel's Operation CRUSH before John Doerr carried them to Google. That lineage explains what OKRs are for: they are the quarterly, measurable expression of a strategy, not a substitute for having one. Read our fuller history in the frameworks shelf.
Writing OKRs that work
Start with the problem, not the sentence. Teams that open a document and try to word an inspiring Objective spend an hour polishing language. Teams that first ask "what would be measurably different if we succeed, and for whom?" find the Objective writes itself, and the Key Results fall out of the answer. Then apply two filters: the Opposite Test, would a sane rival choose the reverse, which checks the Objective is a real choice rather than an operating imperative; and the wildly-important filter, could we drop everything else and still call this the quarter's priority. What survives both is worth betting a team on.
Objective: Make onboarding so effortless that new users reach value in their first session. KR1: Increase first-session activation from 34% to 55%. KR2: Reduce median time-to-first-value from 9 minutes to under 3. The Objective inspires; the Key Results decide.
How many OKRs should a team have? +
One is the discipline, two is the ceiling. Attention is finite: the more objectives a team runs at once, the less each one gets. If everything is a priority, nothing is.
What is the difference between an OKR and a KPI? +
A KPI monitors ongoing health (business-as-usual); an OKR targets a specific change you are trying to create. A metric that breaks, or that you want to push to a new level, graduates into an OKR, then returns to the scorecard when the work is done.
Should OKRs be tied to pay? +
Not at team level. Wiring cash to goal scores converts candour into arithmetic: teams sandbag targets to protect the bonus, and the system loses the honesty it runs on.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
Reading about OKRs is not the same as running them. We install the full system, consulting, coaching and the AI Business OS, and build the capability that stays with your team.