layman/terms
When things break

Incident and post-mortem

in · sih · dunt and pohst · mor · tum

In shortAn incident is when something important breaks and people drop everything to fix it. A post-mortem is the calm meeting afterwards to work out why it happened and how to stop it happening again.

When the alarm goes off, everyone knows their job. Afterwards, someone asks how it could go better next time.

When the fire alarm rings in an office, nobody holds a meeting. Everyone follows the plan: stop work, take the stairs, gather outside. Afterwards there’s a short debrief: the back door was blocked and the alarm was hard to hear upstairs. Next time those things are fixed.

An incident is the alarm going off: something important breaks and people drop everything to fix it. A post-mortem is the debrief afterwards: an honest look at why it happened and what to change.

During an incident

After: the post-mortem

Once things are calm, the team writes up what happened, how long it lasted, who it affected, why it happened and what they’ll change. The changes are the point. A post-mortem with no follow-up is just a story.

Why “blameless” matters

Most incidents have more than one cause: a small mistake plus a missing check plus an alarm nobody saw. If the meeting hunts for someone to blame, people stop speaking up. If it hunts for gaps, the same thing doesn’t happen twice.

Where the comparison breaks down

A fire drill is planned practice. A real incident arrives without warning, often at night. But teams that practise, with drills and written plans, handle the real thing much better.

How the words fit together

Monitoring usually raises the alarm that starts an incident. A rollback is a common way to stop the damage, and logs show what went wrong. Every incident eats into uptime.

Pro tip

A good post-mortem is blameless. It asks what let the mistake happen, not who made it. People who fear blame hide problems.

When you'll hear it

“We've declared an incident.” Something important is broken and a team is now working on it as top priority.

“Who's the incident lead?” Who is in charge of fixing it and keeping everyone updated?

“Let's write up the post-mortem.” Let's write down what happened, why and what we'll change.

Say it in a meeting

“After the last outage, did we change anything or did we just fix it and move on?”