//Postmortem Template
Postmortem Template
Instructions:
- Copy this template and rename it to the following format: “Hyperscalar – Postmortem – ImpactStartdate (YYYY/MM/DD)”
- Add Label for the Hyperscalar
- Add label for status of the Postmortem (In progress, Under Review, Complete)
- See Postmortem Template – How To for a step-by-step guide on how to use this template with descriptions of what is required.
Postmortem Owner:
Incident Date:
Current Status of Incident:
Postmortem Review Date:
Executive Summary
Impact:
Root Cause:
Problem Summary
| Timeline | |||
| Date (mm/dd/yyyy) | Time (ET) (24 hour clock) | Delta from “Incident Start” (hours, minutes) | |
|---|---|---|---|
| Incident Start | – | ||
| Time of Detection (TTD) | |||
| Time of Notification (TTN) | |||
| Time of Engagement (TTE) | |||
| Time of Mitigation (TTM) |
Impact
End-User/Customer Impact:
QoS/SLA Impact:
Service(s) Responsible:
Product(s) Impacted:
Service(s) Impacted:
Ticket(s) resulting from this incident:
The 5 Whys
Define the Problem:
- Why?
- Why?
- Why?
- Why?
- Why?
Root Cause Detailed Summary
What Happened?
Contributing Factors:
If this was a repeat outage, please provide tracking:
If this was a repeat outage, how does manifestation differ?
If the outage was caused by a change, please provide tracking:
Detection and Mitigation
Detection Source:
Detection Details:
| Detailed Mitigation Steps & Respective Timeline | ||
| Date/Time | Crucial Information / Mitigation Steps | Jira Tracking (if applicable) |
|---|---|---|
Postmortem Action Items
| Action Items | |||||
| Action Item | Type | Priority | ETA to Complete | Owner | Jira Tracking |
|---|---|---|---|---|---|
Lessons Learned
What went well?
What didn’t go so well?
Supporting Information (optional)
Glossary (optional)
- 0 Comment
Recent Comments