World map

 

BM

World O4: The Diary & One Order

Blameless postmortems

You will learn: to write down what happened so the system gets better, not so someone gets blamed.

Checked with Prometheus 3 on 1 Nov 2026

The problem

After the A1041 incident, the boss asks: “Who broke it?” Ben gets told off. What happens the next time someone makes a mistake?

Watch

Swipe right for a blameless sentence. Swipe left for a blaming one.

Swipe right for good, left for needs work. Or use the buttons.

1 / 4

The 17:30 change dropped an index, and no check caught it.

A blameless postmortem: A written look back after an incident. It asks what made the mistake easy, never who to blame. asks what made the mistake easy. Never who to punish.

Watch

Top of the postmortem first. Put these in order. Use the arrows, or drag.

  • Summary: one paragraph
  • Impact: who felt it, for how long
  • Causes: what let it happen
  • Timeline: what happened when
  • Action items: owner and date

Put the parts of the write-up in order.

Predict

Which action item will really get done?

Check

A draft postmortem. Tap every line that blames a person.

0 of 2 found

Find the blame, then imagine the system fix behind it.

You did it!

You can now write a blameless postmortem with real action items.

Go deeper (optional)

Write one when customers felt it, data was lost, or on-call stepped in. Share it widely: other teams have the same gaps. Celebrate the people who spoke up first.