Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
minLevel2
maxLevel2
typeflat
separatorpipe

📋Incident overview

Postmortem owner

Incident

Pilot in charge

Visual Observers

Related incidents

Priority

Status
colourRed
titleP1
/
Status
colourYellow
titleP2
/
Status
titleP3+

Affected services

Incident date

Incident duration

Incident response teams

Incident responders

🔮 Executive summary

Incident date

Approx. Damage Costs

Report Date

🔮 Executive summary

⏱ Incident timeline

Describe (approximate) timelines, cross correlate with telemetry/video recordings/etc if any.

⛑ Postmortem report

Instructions

Report

(warning) Leadup


List the sequence of events that led to the incident.

🙅‍♀️ Fault


Describe what didn't work as expected. If available, include relevant data visualizations

.

🥏 Impact

Describe how internal and external users were impacted during the incident. Include how many support cases were raised

.

👁 Detection


Report when the team detected the incident and how they knew it was happening. Describe how the team could've improved time to detection.

🙋‍♂️ Response


Report who responded to the incident and describe what they did at what times. Include any delays or obstacles to responding.

🙆‍♀️ Recovery


Report how the user impact was mitigated and when the incident was deemed resolved. Describe how the team could've improved time to mitigation.

🔎Five whys root cause identification


Run a 5-whys analysis to understand the true causes of the incident.

🗃Related records


Check if any past incidents could've had the same root cause. Note what mitigation was attempted in those incidents and ask why this incident occurred again.

🤔 Lessons learned


Describe what you learned, what went well, and how you can improve.

⏱ Incident timeline

✅ Follow-up tasks

...

Issue

...

Owner

...

Action items

...

Documentation

  •  
  •  

✅ Recommendations for future

Actionable Recommendation

Reasoning