Incident Postmortem template
by Atlassian
Analyze incidents in a structured & blame-free environment
KEY FEATURES
CATEGORIES
Use this template as a framework for learning and turning problems into progress. Discuss the details of an incident: why it happened, its impact, any actions taken, and what should be done to prevent it from happening again.
- How to
- Why Confluence?
How to use the Incident Postmortem template
Ground Rules
This is a safe space for sharing feedback:
Listen with an open mind
Remember that everyone’s experience is valid
Focus on finding the root cause, rather than placing blame
Step 1: Summarize the incident
Include what happened why the severity of the incident and how long the impact lasted.
Stick to the facts. Avoid individual behavior or naming names. You can use sticky notes below to fill in the blanks.
Step 2: Add in details
Add any notable lead-up events any starts of activity the first known impact and escalations. Note any decisions or changes made and when the incident ended along with any post-impact events of note.
Add this before the session to save time.
Step 3: Analyze
Begin with a description of the impact and ask why it occurred. Note the impact that it had. Ask why this happened and why it had the resulting impact. Then continue asking why until you arrive at a root cause.
Add sticky notes to question why and answer because as many times as need be.
Step 4: Reflect
Reflect as a group on actions, related incidents, and opportunities.
Related Templates
Incident communication
Use this template to create a guide for how to respond when things go wrong.
Incident communication
Use this template to create a guide for how to respond when things go wrong.
Retrospective
What went well? What could have gone better? Crowdsource improvements with your team.
ITSM runbook
Use the ITSM runbook template to document the procedures for recurring ITSM alerts and outages.
