What is an OKR Review?

An OKR Review is a structured end-of-cycle evaluation where a team scores its Objectives and Key Results, discusses what drove the outcome, and decides what carries into the next quarter. It sits at the close of an OKR cycle, runs after the final check-in, and combines quantitative scoring with a candid retrospective on learning and execution.

TL;DR

Closes the quarter, not the week: The OKR Review is the end-of-cycle session that grades Key Results and decides what carries forward, distinct from weekly check-ins and the standalone retrospective.
Four ingredients, in order: Score Key Results, evaluate Objective relevance, surface what worked and what did not, and adjust the next cycle's plan.
Cadence is the differentiator: Deloitte found organizations that review goals quarterly or more often are nearly 4x more likely to score in the top tier of its Total Performance Index.
Most failures are structural: Inflated scores, missing data, and "review theater" without follow-up actions are the three patterns that quietly kill the ritual.

Definition: An OKR Review is a structured evaluation process where organizations, teams, or individuals assess their progress towards achieving Objectives and Key Results (OKRs) over a set period, usually quarterly.

How the OKR Review fits inside the quarterly cycle

The OKR Review is one of three review touchpoints in an OKR cycle, and confusing them is the most common reason teams under-use the framework. The weekly check-in tracks progress, the end-of-cycle retrospective examines process, and the OKR Review scores outcomes. Each has a different question, owner, and output.

Ritual	Cadence	Primary question	Output
OKR Check-in	Weekly	Are we on track?	Confidence score, blockers
OKR Review	Quarterly (end of cycle)	Did we achieve what we set out to?	Key Result scores, lessons, decisions
OKR Retrospective	Quarterly (after review)	Is our OKR process working?	Process improvements

Running these as a single meeting collapses the signal. Scoring outcomes in the same session where teams negotiate next quarter's Objectives encourages sandbagging, and process complaints crowd out honest scoring. Keep the OKR Review focused on the outcomes of the cycle that just ended.

The four components of an effective OKR Review

An effective OKR Review covers four components in sequence, and skipping any one weakens the next.

Objective Assessment: Evaluate whether each defined Objective is still relevant, ambitious, and aligned with the broader organizational goals. An Objective that no longer matters should be retired, not re-scored.
Key Result Evaluation: Score each Key Result on the 0.0 to 1.0 scale popularized by Google, where 0.7 represents strong but stretching progress on an aspirational target. See OKR scoring for the standard rubric.
Reflection on Successes and Failures: A candid discussion about what worked, what did not, and why. The 0.4 Key Result that taught the team something is more valuable than the 0.9 that revealed nothing.
Action Plan Adjustment: Decide which Objectives carry forward, which are retired, and what changes in the next cycle's plan. The review is wasted unless it produces decisions.

Tracking progress in a steady cadence, quarter by quarter, month by month, sometimes weekly, in staff meetings against the few focused things that matter, is what turns OKRs into a discipline rather than a poster.

― John Doerr, venture capitalist and author of Measure What Matters

Doerr's emphasis on cadence explains why the review only works when the surrounding rituals do. Without weekly check-ins feeding accurate data into the review, scoring becomes guesswork.

Why the cadence pays off

Frequent goal review is one of the better-evidenced practices in modern performance management. Organizations where employees review personal goals quarterly or more often were nearly 4x more likely to land in the top tier of Bersin by Deloitte's Total Performance Index (Deloitte, 2014). Gallup's Q2 2025 data adds a second finding: only 47% of employees strongly agree that they know what is expected of them at work, and clarity of expectations correlates with 9% higher profitability and 11% higher work quality (Gallup, 2025).

The OKR Review is the structural mechanism that converts both findings into operational practice. It enforces a quarterly checkpoint where expectations are made explicit and outcomes are scored against them.

Where OKR Reviews quietly break

Most OKR Reviews fail in predictable ways, and the failure is rarely about the framework itself.

Inflated scores. When scores feed performance reviews or bonuses, teams sandbag the Objective at the start of the cycle and inflate the score at the end. Decouple OKR scores from compensation; the Google OKR playbook is explicit on this.
Data missing at review time. If the underlying metric has not been instrumented, the review devolves into qualitative debate. Define the data source for every Key Result during planning, not at the review.
No decisions exit the room. A review that produces only scores and not decisions is a status meeting. Every OKR Review should end with at least one of: an Objective retired, a Key Result definition fixed, or a structural change to the next cycle's plan.
The review replaces the retrospective. Process problems get raised, then drown out scoring. Run the retrospective as a separate session in the following week.

The contrarian read: if your team is shipping, learning, and adjusting on its own, a heavy review process can slow it down. Light reviews fit small teams with high information density. Formal reviews earn their cost in organizations large enough that alignment is the bottleneck.

How to run an OKR Review meeting

Implementing the review well is mostly about preparation and follow-through, not the meeting itself.

Score asynchronously before the meeting. Each Objective owner submits Key Result scores 48 hours ahead. The meeting discusses why, not what.
Time-box the scoring discussion. Five to seven minutes per Objective. Long debates indicate the Key Result was poorly defined; fix it for next cycle rather than re-litigating it.
Invite the right people, not everyone. Objective owners, their managers, and direct contributors. Optional observers if alignment matters; not an all-hands.
End with explicit carry-forward decisions. Document which Objectives continue, which are retired, and what data instrumentation needs to land before the next cycle starts.
Use OKR software to capture scores and decisions so the next cycle's planning starts from data, not memory.

OKR Reviews as the input to the next cycle

The OKR Review's most under-used output is its role as planning input for the next quarter. Objectives that scored 0.3 to 0.4 often signal a Key Result definition problem, not a team performance problem. Objectives that scored 0.9 to 1.0 were probably sandbagged and need a more ambitious framing.

The review surfaces both, and an OKR champion or program owner can use the patterns across teams to refine the OKR planning process itself.

Organizations that treat the review as a closing ritual leave most of its value on the table. The discipline is in the handoff.

How often should you run an OKR Review?

Most organizations run OKR Reviews once per quarter at the end of each cycle. Companies running monthly OKRs review monthly; companies with annual Objectives run a mid-year checkpoint plus a year-end review. The OKR Review is distinct from the weekly check-in, which tracks ongoing progress.

What is the difference between an OKR Review and an OKR Retrospective?

The OKR Review scores outcomes and decides what carries forward; the OKR retrospective examines the process itself, including whether the cadence, tooling, and Objective-setting approach worked. Running them as one meeting causes process complaints to drown out honest scoring, so most teams separate them by a week.

How do you score Key Results in an OKR Review?

Score each Key Result on a 0.0 to 1.0 scale, where 0.7 represents strong progress on an aspirational target and 1.0 represents full delivery. Score asynchronously before the meeting using the underlying metric, not opinion, and reserve the meeting for discussing why the score landed where it did. See OKR scoring for the full rubric.

Who should attend an OKR Review?

Objective owners, their direct managers, and the contributors who did the work. Keep the meeting focused, not all-hands. For company-level Objectives, the leadership team attends; for team-level Objectives, the team and its manager are enough.

Should OKR scores be tied to performance reviews or bonuses?

No. Linking OKR scores to compensation incentivizes sandbagging at goal-setting and inflated scoring at the review, which corrupts both rituals. Keep OKR scoring separate from performance management and use a separate process for individual performance reviews.

What makes an OKR Review effective?

An effective OKR Review produces decisions, not just scores. It ends with explicit carry-forward choices, surfaces Key Result definition problems for next cycle, and feeds the data back into OKR planning. Reviews that produce only scores are status meetings in disguise.