How to Close Post-Mortem Loops into the Plan
This skill is what makes the operating system compound. Post-mortems convert misses, incidents, and surprising wins into changes to the plan, the standards, and the cadence itself. Without the loop closed, the same variance returns every quarter with new names attached.
Developing
Start here. Build the foundation.- 1
Define the triggers in writing: a plan miss beyond an agreed threshold, any operational incident, a result that beat plan for unclear reasons. Book the review within days of the trigger while memory is fresh, and run the same discipline on a win early; it teaches the organization the review is about learning, not punishment. You are done when reviews happen by rule, not by mood.
- 2
Open each review by stating the goal is how the system produced this, then keep pulling the thread past the first human error to what made that error easy. The room is right when people volunteer their own missteps without being cornered.
Proficient
Build consistency and rhythm.- 3
Before the room empties, convert findings into specific changes: a target revised, a standard rewritten, a step added to the cadence, each with one owner and a date. Findings parked as lessons learned count as nothing. The record of the review should read like a change order.
- 4
Put a check on the calendar thirty to sixty days out: did the change land, has the failure mode recurred. A recurrence reopens the original review rather than starting a fresh one that rediscovers the same cause. It works when repeat incidents become rare enough to be news.
Mastered
Operate at the highest level.- 5
Twice a year, read across the reviews: which causes repeat, which fixes held, and publish the patterns where teams can apply them before their own incident. The proof is a team adopting a prevention for a failure they never experienced. Proficiency fixes what happened to you; mastery makes the company stop paying for the same lesson twice.
Common Pitfalls
Avoid the common failure modes.- Reviewing only catastrophes. If the review only appears when something burns down, everyone learns that reviews are punishment and starts hiding the smoke.
- Action items assigned to teams instead of people. A change owned by a team is owned by nobody, and it will still be open at the next review.
- Fixes that live in someone's memory instead of the plan or a standard. They evaporate at the next reorganization, and the failure returns with new names attached.