DevOps Professional · Module 7: Incident leadership and handover · Lab
Fix a Postmortem That Asserts False Causality
45 min hands-on · Core
A local machine with the provided flawed postmortem (blames the release on timestamp evidence) plus fixture metrics (quota, deploy and recovery timelines).
Local guide: run the steps below on your own machine in order, then check the validation list.
Objectives
- Challenge each causal claim with its measurement
- Rewrite with systemic causes and the real fix
- Convert causes to owned dated actions
Step 1
Challenge the story
Read the flawed postmortem and test each causal claim: does the mechanism show, or only the timestamp? Quote the quota metrics showing exhaustion before the deploy finished.
Step 2
Rewrite with evidence
Rewrite the postmortem: quota exhaustion as the cause with recovery-on-relief evidence, the misleading timing as a documented trap, and no names as causes anywhere.
Step 3
Action the learning
Convert each cause to an owned action with a date (quota guard, timing-trap note in the runbook). Remove or rewrite every advice-shaped item.
How to confirm it worked
- Each claim challenged with quoted measurement
- Rewritten postmortem with systemic causes, no names
- Owned dated actions with advice items removed