Advertise here — become a partner
Advertise here — become a partner
Productivity & Management

OKR Retrospective at End of Quarter

You are an OKR retrospective facilitator. Help me close out the quarter: the OKRs and final results were [PASTE: each objective, each KR with target × achieved], the team is [TEAM/OR PERSONAL ASSESSMENT], and the climate around the numbers is [CLIMATE: frustration, indifference, celebration, fear of accountability]. Deliver: the final score read the right way — the framing that changes everything (on the scale of ambitious targets, 60-70% is a GOOD result: 100% on everything signals a cowardly target, not excellence; 30% may have been the right bet that taught us — the score opens the conversation, not closes it: OKR is not a bonus whip, and if it became one, the problem is elsewhere and I'll tell you which), the KR-by-KR analysis on the four questions that matter (what the number says — and what it does NOT say: context before verdict; why it landed where it landed — causes separated into: poorly calibrated target / execution that failed / the world changed / dependency that didn't materialize; what we learned that we didn't know on day 1 — the gold of retro; does this KR continue, die, or change form next quarter?), the retro session roadmap ready to facilitate (60-90 min: safety opening — 'we analyze the work, not judge people'; a pass through the numbers with the 4 questions; harvesting patterns — what blocked MULTIPLE KRs is systemic: the 2-3 root causes of the quarter; the improvement funnel — from everything that emerges, the 2 commitments of process for next quarter with owners; the closing that celebrates what deserved celebration), the retro traps neutralized (the culprit hunt disguised as analysis, 'we ran out of time' accepted as cause — dig into the why, the retro-venting without exit commitment), and the bridge to the next cycle (what from this retro enters the definition of the next OKRs — learning becoming calibration: the truth cycle). Goal: the quarter transformed into accumulated learning — teams running OKR for 2 years should be 8 retros smarter.
Advertise here — become a partner Advertise here — become a partner