Guidelines for Conducting Effective OKR Retrospectives

Author: vivo Internet Platform Product R&D Team

This article is the first summary in the "OKR Sword" series, focusing on the importance of OKR retrospectives within the OKR lifecycle. It explains what an OKR retrospective is, why it should be conducted, shares the team’s practical experiences and improvements, and extracts key points for running a successful OKR retrospective meeting.

1. Introduction to OKR Retrospectives

The term "retrospective" originated from the game of Go and later entered project management as a popular internet buzzword. While retrospectives are often associated with incident reviews and can feel punitive, they can also reduce incidents and improve project delivery quality.

However, negative side‑effects such as group division, fear of mistakes, and blame‑shifting may arise if not handled properly.

Mitigation approaches

No punishment. The team treats retrospectives as self‑analysis, acknowledging the psychological cost already incurred.

Replace formal meetings with short sharing sessions. A 15‑minute "flash" sharing gives the person who made the mistake ownership of the narrative, promotes learning, and reduces the feeling of a punitive meeting.

2. What is an OKR Retrospective?

It is a crucial stage in the OKR lifecycle, acting as a bridge between quarters. It provides a summary of the current quarter’s execution and inputs for the next quarter’s OKR setting.

OKR retrospectives are not blame sessions; they are self‑examination, periodic summarisation, and a means for the team to achieve continuous improvement.

The main content includes self‑rating, goal review, process review, loss‑gain analysis, and pattern summarisation.

3. Why Hold an OKR Retrospective?

Beyond incident analysis, retrospectives help individuals and teams consolidate fundamentals, expand capabilities, gain respect, and achieve self‑actualisation. They also enable objective assessment of user value, company value, and personal growth.

4. How to Conduct an OKR Retrospective

The team evolved through two major versions of the process.

2.1 First Version ("Han Dan Xue Bu")

Personal preparation: Each member scores their OKR, reflects on gains and losses.

Meeting discussion: Individual retrospectives, data synchronisation, analysis of success/failure reasons.

Group feedback: Peers provide concrete suggestions.

Conclusion output: Praise good performance, summarise issues, set direction for the next quarter.

The template (Fig. 1‑6) guided members to fill self‑rating, goal review, process review, loss‑gain analysis, and pattern summarisation.

2.2 Improved Version

Addressing issues such as overly heavy templates, dull atmosphere, lack of team‑level visibility, and insufficient rewards, the second version shifted focus from individual to team, simplified templates, added award mechanisms, and introduced a dedicated OKR coach.

Key steps include:

Personal preparation: Simplified self‑assessment template (Fig. 1‑9).

Team preparation: OKR coach prepares concise materials, snacks, and awards.

Team retrospective: Each owner presents team‑level OKR progress with clear percentages.

Individual retrospective: Randomised order, focus on achievements, shortcomings, and improvement actions.

Group feedback & conclusion: Positive, constructive comments, followed by a summary for the next quarter.

Award ceremony: Voting or leader‑selected awards, including tangible prizes and recognition.

2.3 Future Versions

Experiments include removing personal retrospectives for large teams, involving managers in the process, and varying award selection methods. The core principle remains: a lightweight, team‑centric, positively reinforced retrospective.

5. Key Points for a Good OKR Retrospective

Goal‑driven, not tied to performance evaluation. Avoid linking OKR completion directly to compensation to prevent gaming and loss of honesty.

Positive reinforcement, not blame. Encourage sharing of failures as learning opportunities.

Transparency and honesty. Present both good and bad results objectively.

6. Summary

To run an effective OKR retrospective, simplify templates, strengthen team‑level reviews, prepare enjoyable rewards, and ensure fair voting for awards. A skilled moderator can further enhance the session. The next article will discuss how to evaluate performance under OKR.