How to run a quarterly OKR review that grades honestly, learns systematically, and resets ambitiously.
OKRs are a learning system, not a scorecard
The single biggest reason OKRs fail inside companies is that the quarterly review is run as a scorecard exercise rather than a learning exercise. When the meeting is about defending the score, key results get sandbagged, objectives get watered down, and the entire system devolves into a reporting layer with extra steps. The functional version of an OKR review treats the score as the input to a structured conversation about what was learned, what surprised the team, and what the next quarter's objectives should change as a result. The score matters, but the score is the beginning of the meeting, not the end of it.
Grade honestly, then explain the gap
Each key result should be graded on a 0.0 to 1.0 scale at quarter-end, with an honest explanation of the gap between the grade and the original target. The explanation matters more than the grade. A 0.4 with a clear explanation that the team learned the wrong thing was being measured is more valuable than a 0.7 with no explanation. The discipline is to force every team to write three sentences for each key result: what they actually achieved, what they learned about the underlying assumption, and what they would change in next quarter's key result as a result of that learning. Without those three sentences, the review is theater.
The three-question structure that makes the review productive
Every key result review should answer three questions in this order: what number did we hit, what did we learn, and what changes next quarter. The first question is the score. The second question is the post-mortem. The third question is the input to the next planning cycle. If a key result misses, the third question forces the team to either change the target, change the strategy, or kill the initiative — sandbagging the next target is not a valid response. If a key result over-delivers significantly, the third question forces the team to ask whether the target was set ambitiously enough or whether the team got lucky. Both directions matter.
For a deeper companion read on this topic, see our recommended editorial guide.
The review pack: format that drives the conversation
The review deck should be structured one slide per objective, with the key results as a small table at the top of the slide showing target, actual, score, and a one-sentence learning. The bottom of the slide is a free-text section explaining what the team would do differently and what the next quarter's objective should be. The pack should be circulated 48 hours before the live review so reading the pack is not the meeting — debating the pack is the meeting. This single change to the format transforms the energy of an OKR review from defensive reporting into collaborative recalibration.
Setting the next quarter without re-litigating the last one
The most common failure mode of OKR reviews is to spend 80% of the meeting grading the previous quarter and 20% setting the next one. That ratio should be inverted. The previous quarter's grades should be a thirty-minute walkthrough; the next quarter's objectives should be a ninety-minute working session. The structural fix is to require every team to come into the review with a draft of the next quarter's objectives already written, anchored on the learnings from the previous quarter. The meeting then becomes a critique of the draft, which is far more productive than building it from scratch in the room. The deck format should make this easy by giving each objective a parallel 'next quarter draft' slide adjacent to its current-quarter review slide.
Working through this with your team? Our recommended workshop facilitation guide has a battle-tested run-of-show.
Templates that pair with this guide
The templates below are pre-structured around the playbook in this guide. Each one ships in both Google Slides and PowerPoint, and the master grid is set up for the slide-by-slide pacing the guide recommends.