Copy these headings into your own document. Write what you can show. If you don’t have a number, say so instead of guessing one.
This document is for learning. It isn’t an input to performance management, compensation, or promotion.
The blameless postmortem guide explains why the sections are shaped this way.
Summary
A few sentences. What broke, who was affected, when user impact started and stopped, and what restored service.
Impact
- User impact started:
- User impact stopped:
- Who was affected, and what they couldn’t do:
- How you know: a measurement, a support signal, or “we don’t have a measurement for this.”
- Where you got lucky:
Timeline
Use one timezone and name it. Each line is a fact. Mark detection, the start of mitigation, the end of user impact, and the close.
- Timezone:
- Timeline:
What went well
What went poorly
Describe conditions. A missing signal, two changes at once, a decision nobody was clearly allowed to make.
Contributing factors
List the combination that produced this outcome. Mark anything that’s still a hypothesis.
Action items
Each item needs an owner and a change you can tell is done. “Be more careful” doesn’t count.
| Action | Owner | Done when |
|---|---|---|
Review
- Facilitator:
- Review date:
- Where this document is shared: