OKR Quarterly Review: How to Evaluate Your OKR Cycle Effectively

What Is an OKR Quarterly Review? Distinguishing It from Retrospectives and Check-ins

The OKR framework includes three core reflection formats: check-in, Quarterly Review, and Retrospective. In practice, these formats are often mixed — with negative consequences for learning quality.

The OKR Quarterly Review takes place at the end of an OKR cycle and answers a central question: What did we achieve, and what do these results mean for the business?

The Three Reflection Formats Compared

The review evaluates results (the Key Results); the retrospective evaluates the process (how the team worked with OKRs). Both formats take place at the end of the quarter but should be conducted separately — ideally the review first, then the retrospective.

Why this separation matters: In the review, the team analyzes the numbers objectively. Were the Key Results achieved? Which Objectives had the greatest impact? The review is about facts and outcomes. The retrospective, by contrast, reflects on the process: Was the OKR cycle too long? Did the check-ins work? Were the OKRs well formulated?

If you mix both formats, here is what happens: The team spends 90 minutes discussing process issues and has no time to systematically evaluate results. Or the reverse: the results presentation consumes the time needed for honest process reflection. You can find detailed guidance on retrospectives in our OKR Retrospective guide.

Remember: The Quarterly Review is not a performance evaluation of individual employees. OKRs are team goals, and the review assesses team progress — not individual performance.

Timing and Preparation: How to Plan Your OKR Review

A good OKR Quarterly Review requires preparation. Without pre-collected data and a clear structure, the meeting devolves into an aimless discussion.

The Ideal Timeline

Schedule the review in the last week of the quarter, not the first week of the new quarter. The review results feed directly into the OKR Planning of the next cycle.

Preparation by OKR Owners

Each OKR owner should prepare the following information before the review:

1. Final score for each Key Result (methodology covered in the next section) 2. Context for the results: Why was a Key Result exceeded or missed? What external factors played a role? 3. Lessons learned: What would the team do differently next time? 4. Impact assessment: Did achieving the Key Result actually contribute to the Objective? Sometimes all Key Results are met but the Objective remains unachieved — a sign of poorly chosen metrics.

Preparation by the OKR Champion

The OKR Champion or OKR Master consolidates results across all teams and prepares an overall summary:

• Company OKRs: Overall score and highlight results
• Team OKRs: Summary per team with notable findings
• Cross-functional dependencies: Where did teams support or block each other?
• Trend analysis: How are scores developing across multiple cycles?

In Northly, this data can be aggregated automatically. Instead of manually merging spreadsheets, the tool generates a review overview with scores, trends, and comments — saving the OKR Champion several hours of preparation time.

Scoring Methods: How to Evaluate OKR Results Properly

There are several methods for evaluating OKR results. Choosing the right approach depends on company culture and OKR maturity.

Method 1: The 0.0–1.0 Scale (Google Method)

The best-known scoring method comes from Google. Each Key Result is rated on a scale from 0.0 to 1.0:

With Google's Moonshot OKRs, a score of 0.7 counts as success. The logic: If you regularly hit 1.0, your goals were not ambitious enough. For Committed OKRs, by contrast, 1.0 achievement is expected.

The Objective score is the average of the Key Result scores. Example:

• KR1: 0.8
• KR2: 0.5
• KR3: 0.7
• Objective score: 0.67

Method 2: Traffic Light System

For companies that prefer a simpler evaluation, the traffic light system works well:

• Green: Key Result achieved or exceeded
• Yellow: Clear progress, but goal not fully reached (50–80%)
• Red: Little or no progress (< 50%)

Advantage: Intuitive communication, even for OKR beginners. Disadvantage: Less granularity, making trend analysis across multiple cycles harder.

Method 3: Confidence Level

A modern variant tracks confidence (the belief that the Key Result will be achieved) throughout the entire cycle:

• At the start of the quarter: 50% confidence (the "sweet spot" for ambitious goals)
• Weekly updates: Is confidence rising or falling?
• At quarter end: Actual result vs. initial confidence

This method provides valuable data for OKR scoring: It shows not just what was achieved but also how the assessment changed over the course of the quarter. A Key Result that starts at 50% confidence and ends at 90% may have been too easy. One that drops from 50% to 20% signals early that something is off.

Recommendation: Start with the 0.0–1.0 scale and add confidence tracking once your team has experience with OKRs. The combination of both methods yields the most differentiated results.

The Review Meeting Agenda: 90 Minutes That Make the Difference

A well-structured review meeting is the heart of the Quarterly Review. Here is a proven agenda for a 90-minute format:

Suggested Agenda (90 Minutes)

Block 1: Set the Context (10 Minutes)

• Welcome and meeting objective
• Overview: How was the quarter overall? Market developments, team changes, special challenges
• Reminder of ground rules: No blame game, focus on learning

Block 2: Review Company OKRs (20 Minutes)

• Present overall score for company OKRs
• Briefly discuss each Objective: score, highlights, lowlights
• Question: Did achieving the Key Results actually contribute to the Objective?

Block 3: Review Team OKRs (40 Minutes)

• Each team presents its results (5–7 minutes per team)
• Format per team: Objective, Key Results with scores, context, key learning
• Questions from the group: What can we learn from this team? Where were there dependencies?

Block 4: Identify Patterns (15 Minutes)

• What patterns stand out? Which topics were exceeded or missed?
• Cross-functional dependencies: Where did alignment work, where did it not?
• Which OKRs should be continued, modified, or retired next quarter?

Block 5: Outlook and Wrap-up (5 Minutes)

• Summarize the top 3 learnings of the quarter
• Implications for the next OKR Planning
• Set next steps and dates

Facilitation: Dos and Don'ts

• Do: Celebrate results — including partial wins. A score of 0.6 on an ambitious moonshot deserves recognition.
• Do: Ask open-ended questions. "What surprised you?" works better than "Why didn't you achieve this?"
• Don't: Hold individual employees responsible for low scores. OKRs are team goals.
• Don't: Use the meeting for detailed operational discussions. Keep the focus on results and patterns.
• Don't: Skip the review "because there is no time." A cycle without a review is a cycle without learning.

For smaller teams (under 10 people), 60 minutes is sufficient. For company-wide reviews with multiple departments, plan 2 hours and use a structured presentation format so each team can share its results efficiently.

Analyzing Results: What to Do at 30%, 70%, or 100% Achievement

Scores alone say little. What matters is the interpretation — and that depends on whether the OKR is a Committed OKR or a Moonshot OKR.

Scenario 1: Score Below 40% — "Red"

For Committed OKRs, this is a serious signal. The agreed-upon delivery did not happen. Analyze:

• Was the goal realistic but execution failed? Then solve the execution problem
• Was the goal unrealistic from the start? Then improve the formulation
• Did conditions fundamentally change? The goal may have been right but was made impossible by external factors

For Moonshot OKRs, a score of 0.3 is disappointing but not catastrophic. The question is: Was enough learned to do better on the next attempt?

Scenario 2: Score 50–70% — "Yellow"

The most common zone — and the hardest to interpret.

• 0.5 on a Moonshot: Good progress. Direction is right, ambition level was appropriate.
• 0.5 on a Committed OKR: Warning signal. Half the delivery is missing. What was the blocker?
• 0.7 on a Moonshot: Outstanding. The team achieved 70% of an extremely ambitious goal.
• 0.7 on a Committed OKR: Narrowly missed. Often the issue was lack of prioritization or resources in the last month of the quarter.

Scenario 3: Score 90–100% — "Green+"

For Committed OKRs: Excellent execution. Celebrate the result.

For Moonshot OKRs: Be cautious. If Moonshot OKRs regularly land at 1.0, they are not ambitious enough. A moonshot should push the team out of its comfort zone. 100% achievement on a true moonshot is either an exceptional success — or a sign the bar was set too low.

Assessing the Quarter as a Whole

Do not just look at individual OKRs — consider the big picture:

• What is the score distribution? A healthy portfolio has a mix of red, yellow, and green.
• Do low scores correlate with specific teams, topics, or time periods?
• Is there a pattern among over- or under-performing OKRs?

This analysis becomes easier when you track your OKRs in a tool like Northly. There you can visualize score development across multiple cycles and identify patterns that remain invisible in individual spreadsheets.

Documenting Learnings: Building Organizational Memory

The most valuable output of a Quarterly Review is not the scores — it is the learnings. Yet in most organizations, these insights are lost because they are not systematically documented.

What Should Be Documented

For each Objective, a standardized learning format is recommended:

1. Results Summary - Objective and final Key Result scores - Was the Objective a committed or moonshot? - Was the Objective achieved overall (regardless of Key Result scores)?

2. Context and Influencing Factors - What internal factors influenced the result? (Resources, priorities, team changes) - What external factors? (Market shifts, customer behavior, regulatory developments) - What was the biggest surprise?

3. Methodological Learnings - Were the Key Results well chosen? Did they truly measure the Objective? - Was the ambition level appropriate? - Did the check-ins work? Were problems identified early enough?

4. Recommendations for the Next Cycle - Should the Objective be continued? - Which Key Results should be adjusted? - Which initiatives worked and should be scaled?

The Learning Log

Maintain a cross-cutting learning log that captures the key insights from each cycle. After 4–8 cycles, this becomes a valuable organizational memory:

• How has OKR quality developed across cycles?
• What typical mistakes has the organization overcome?
• In which areas are there recurring problems?

Best Practice: Make learning documentation a mandatory part of the review process. No review is complete until the learnings are captured in writing. In the rush of the new quarter, verbal insights are otherwise lost within days.

Documenting learnings is also valuable for new team members. Instead of repeating the same mistakes, new colleagues can read about what the organization has already learned — an underestimated competitive advantage that grows with every OKR cycle.

From Review to the Next Cycle: Managing the Transition

The Quarterly Review is not an isolated event — it is the starting point for the next OKR cycle. The transition between two cycles is one of the most critical phases in the OKR rhythm.

The "OKR Week" — A Proven Structure

Many successful OKR organizations establish an "OKR Week" at the quarter transition:

What Flows from the Review into Planning

The review delivers three types of input for the next OKR Planning:

1. Continued OKRs: Objectives that have not yet been achieved and remain strategically relevant. Adjust the Key Results based on new insights rather than carrying them over unchanged.

2. New OKRs based on learnings: Insights from the review can inspire new Objectives. Example: The review reveals that customer satisfaction dropped despite strong feature delivery — leading to a new Objective around customer experience.

3. Retired OKRs: Not every Objective needs to be continued. If a topic has lost its strategic relevance or has been displaced by other priorities, retire it deliberately — rather than continuing it out of obligation.

Common Traps in the Transition Phase

• Copy-paste OKRs: Carrying the same OKRs into the new quarter with slightly adjusted numbers. If the Objective stays the same, ask: Did we actually learn anything?
• Planning gap: Two weeks pass between the review and new planning, during which the team works without OKRs. Keep the transition phase short.
• Overloading: Setting too many OKRs in the enthusiasm of the new quarter. The recommendation stands: a maximum of 3–5 Objectives per team.

A solid Quarterly Review forms the foundation for continuous improvement. Each cycle should be qualitatively better than the last — better OKR formulations, more precise Key Results, more realistic ambition levels. When that happens, the OKR process becomes a genuine competitive advantage: an organization that systematically learns from its own experiences and pursues its strategic goals with increasing precision.