Skip to content
BENIBIX Learn

Postmortem

Infrastructure📟 ReliabilityIncident Response

Also known as Post-Mortem, Incident Review, Blameless Postmortem, Post-Incident Review

A written review after an incident. It finds causes and fixes, not someone to blame.

Think of it like

It is like watching the replay after a game. The team sees what went wrong, so it does not happen twice.

Example

After a 20-minute checkout outage, Jack's team writes a postmortem. It finds a test that never ran, and adds two action items with owners and dates.

Why it matters

Without one, the same failure comes back. With one, every incident makes the system stronger.

Definition

A postmortem is a written review of an incident after it is over. It records what happened, how users were hurt, what the team did and why it broke. It ends with actions to stop it happening again, each with an owner. A good postmortem is blameless. It looks for gaps in the system, not for a person to blame.
The postmortem comes last. Its actions loop back so the same break does not happen again.

Common mistake

Naming the person who pressed the button. People then hide mistakes, and the real causes stay.

Key takeaways

  1. 1
    Blameless. Fix the system, not the person.
  2. 2
    Written down. Shared so others can learn from it.
  3. 3
    Actions with owners. Each fix has a name and a date.