Incident postmortem and improvement actions
Full instructions and common questions
Incident postmortem and improvement actions
Use a blameless structure to record production impact, detection, response, causes, contributing factors, timeline, five whys, and corrective actions. Drafts autosave locally.
How to use
- Record the incident date, severity, impact, detection, and recovery.
- Describe root and contributing system conditions; use the five whys to examine causal chains.
- Add timestamped events and corrective actions with clear owners and due dates.
- Review the Markdown report, confirm impact estimates and timezone details, then download it.
Try an example
Order the timeline from alert through responder arrival, mitigation, and recovery. Phrase corrective actions with a concrete verb, owner, and completion date.
Limits and privacy
Users provide all facts. The tool does not connect to monitoring, tickets, or logs, validate impact estimates, or create engineering tasks. Do not expose personal data, tokens, or customer secrets in a report.
Common questions
Must I fill all five whys?
No. The prompts help explore causes. Stop when the evidence supports a system-level explanation.
Are corrective actions synced to a task system?
No. After exporting, create and track work items in your team’s issue or project system.