Every quarter, leadership runs a retrospective. The themes are honest: we overcommitted, we ignored dependencies, we shipped initiatives without owners, we let the OKR refresh slip. The action items are written down. The deck is shared.
Next quarter, the same themes appear.
Why nothing carries
A post-mortem is a document. A pattern is changed by a structure. If the only artefact produced by the retrospective is a list of lessons in a wiki, the structure of the next planning cycle has not moved. The same incentives, the same calendar, the same goal-setting template will produce the same result. The lessons are real and ignored, not because anyone is lazy, but because the lessons never become rules.
What carries the lesson
- An entry in the planning template that forces the question the lesson raised
- A change to the cadence that puts the earlier signal in front of the team
- A guardrail in the goal-setting tool that won't let the failure mode recur silently
In other words, the lesson has to become part of how the next plan is built, not a document the next plan ignores.
The Vindaris view
Retrospectives are inputs to the operating system, not artefacts in a folder. If the lesson doesn't show up as a structural change before the next planning cycle starts, it didn't land.