DailyWF / Templates
Postmortem Template
Analyze an incident or failed outcome without losing practical lessons.
Template intent
Postmortem Template should be short enough to reuse and specific enough to produce consistent records.
Recommended fields
- Purpose and trigger.
- Owner and contributors.
- Required inputs.
- Main fields or steps.
- Output, evidence, and review trigger.
Expected output
A reusable template that produces consistent records without forcing unnecessary approval language.
Common failure mode
Waiting for certainty before communicating impact and next update time.
Use notes
| Copy style | Keep headings stable but allow local names, tools, and examples to change. |
|---|---|
| Avoid | Do not include fields that nobody will use or review. |
| Review point | Revise after the template produces unclear or inconsistent records. |
Related pages
- Runbook TemplateDocument how to operate, recover, or support a system.
- Change vs IncidentDistinguish planned change from unplanned service disruption.
- Incident NotificationDefine who must be notified when incidents affect service, data, obligations, or reputation.
- Incident Response ChecklistStructure first actions during a lightweight incident response.
- Incident Response LiteCoordinate a small incident without building a heavy response program.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.