Skip to content

Instantly share code, notes, and snippets.

@alexfdz

alexfdz/postmortem_template.md

Created June 8, 2022 12:00
Show Gist options
  • Save alexfdz/b717702d8f320c0224fc269e71c92a10 to your computer and use it in GitHub Desktop.
Save alexfdz/b717702d8f320c0224fc269e71c92a10 to your computer and use it in GitHub Desktop.
Download ZIP
Postmortem template
Raw
postmortem_template.md

YYYYMMDD INCIDENT_NAME

What happened?

Include a timeline

  • Input - when the bug(s) reached production
  • Detection - when the incident was detected. It initiates the incident management process (e.g. SLA for incident resolution starts).
  • Resolution - when the incident was resolved (e.g. through a workaround, final fix, rollback, etc). This is the end of incident management (e.g. SLA for incident resolution ends)

What was the impact?

Explanation of how customers were affected

What went well during the incident handling?

List anything you did well and want to call out. IT’s OK to not list anything.

What did not go so well?

Preventing the incident

What can be done to prevent this kind of incident from happening again?

Improving Detection Time

What can be done to detect the incident earlier / faster / more reliably

Improving Mitigation Time

What can be done to improve our mitigation time?

Describe actions agreed to be done

Describe what was agreed to do. For each action create an issue in the team’s backlog and link them to this postmortem.

  1. Any fixes required to prevent the contributing factor in the future
  2. Any preparedness tasks that could help mitigate the problem if it came up again
  3. Remaining postmortem steps, such as internal communications, status-page public post, …
  4. Any improvements to our incident response process
@alexfdz
Copy link
Author

alexfdz commented Jun 8, 2022

Sources

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment