In a blameless postmortem, the focus is on…
Options
- Finding out who made the mistake so that they can be warned
- The timeline, root causes, contributing factors and action items (Correct option)
- Hiding the incident from the customers until it is solved
- Rewriting the whole system that failed during the incident
Answer
Timeline, root causes and contributing factors, and concrete action items to prevent recurrence
Why
After an incident, the team writes what happened (timeline), why (root causes and contributing factors), what went well, and what to change.
'Blameless' because people act on the information they had at the time; blaming makes people hide mistakes.
The output is concrete action items: better alerts, safer tooling, tests, runbooks.
Remember
Postmortem = learn and fix the system, not blame people.