Member-only story

Incident Postmortem Template

Towards Operational Excellence

Adrian Hornsby
The Cloud Engineer
6 min readJun 24, 2020

I’d like to express my gratitude to my colleague and friend Arni Birgisson for his valuable feedback.

Since I published my blog series Towards Operational Excellence, I received a relatively large amount of feedback. But one question, in particular, stood out.

“Can you share an incident postmortem template?”

In this blog post, I will share an example incident postmortem template, which I hope will help you get started. I will also share some DOs and DON’Ts that I have seen work across a wide variety of customers — both internally in Amazon, and externally.

What is a postmortem?

A postmortem is a process where a team reflects on a problem — for example, an unexpected loss of redundancy, or perhaps a failed software deployment — and documents what the problem was and how to avoid it in the future.

“Postmortems are not about figuring out who to blame for an incident that happened. They are about figuring out, through data and analysis, what happened, why it happened, and how it can be stopped from happening again.” —…

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

The Cloud Engineer
The Cloud Engineer

Published in The Cloud Engineer

All you need to know about building resilient, scalable, and highly available systems in cloud.

Adrian Hornsby
Adrian Hornsby

Written by Adrian Hornsby

Ex-Principal System Dev Engineer @ AWS ☁️ I break stuff .. mostly. Opinions here are my own.

No responses yet

What are your thoughts?