A bad day is not a personality test. It is a problem with how things are set up. A blameless review, also called a post mortem, looks for the conditions that made the failure possible.
A simple shape: what happened, a timeline, who was affected, what made it possible, what went well, where you were lucky, and a few clear changes, each with an owner and a date.
Avoid naming one person as the cause. People act on the information and tools they have. Fix the information and the tools.
End with fewer, better actions. A safety measure that makes the mistake harder beats a reminder to be careful.
Words you will see
- Post mortem
- A written review of what happened and what to change.
- Contributing factor
- A condition that made the failure possible.
- Action item
- A specific change with an owner and a date.
Decision
A key leaked because a teammate pasted it into an AI tool. What is the best change to come out of the review?
What to do instead
- Build the timeline from records, not memory.
- Keep only the actions you will really do.
- Share the review openly.
Common mistakes
- Naming a person as the root cause.
- Writing a long list of actions that never get done.
- Skipping the review after a near miss.
References and further reading
Finished this one?
Add it to What I learned and earn 50 Trust. You can open your list from the badge at the bottom of the page.