Write a retrospective

Once a period wraps up, write a retrospective to review what happened, capture the lessons, and decide whether to raise the bar next time.

1. 1Pick the period — Select a period to view or create its retrospective.
2. 2Create retrospective, and give it a title.
3. 3Read Period summary: Objectives, Key results, Avg progress, Avg grade, Check-ins and Status distribution, with every objective listed by Status, Progress and Score.
4. 4Generate AI analysis — Let AI read the numbers and surface a first-draft narrative — what drove the results, where you over- or under-performed, and what it suggests for next period. You can edit and add your own take below.
5. 5Add Team commentary: Add the human layer: why did this happen, and what do we change next time? Start with a prompt: What went well?, What underperformed and why?, Were our targets right?, Adjustments for next period
6. 6Finalize when it is agreed.

The AI draft is a starting point, not the retrospective. It reads the numbers and says what happened; it cannot know that a key result slipped because the customer postponed, or that you hit a target by dropping something else. That is what Team commentary is for, and a retrospective with only the AI section in it is a report nobody learns from.

Were our targets right? is the question people skip. A period where everything hit 100% is not necessarily a good period — it can mean the targets were safe. Asking it honestly is what stops OKRs quietly becoming a list of things you were always going to do.

Finalizing. Finalizing marks the report as final and locks editing. You can reopen it later if you need to make changes. It then shows Final and Finalized on {{date}}; Reopen unlocks it again, so finalizing early is safe.

Regenerating. This replaces the current AI analysis with a fresh one. Your written commentary is not affected. — your writing survives, so refreshing the AI section after a late check-in costs you nothing.

Refresh stats re-reads the period if goals changed after you created the report.

Do it while people remember. A retrospective written three weeks into the next quarter is an exercise in reconstruction, and the adjustments it produces arrive too late to change anything.