MYTH: "Blameless means we skip naming who acted."

MYTH: "Blameless means we skip naming who acted."
The correction: blameless means we don't punish, not that we stay vague. "Someone deployed Friday" can't be fixed; "the deploy gate didn't block Friday" can.

SOP: Blameless postmortem
Run this whenever an incident lasts longer than 15 minutes.

Stage 1 — Timeline
— ☐ Write what happened in order, with timestamps and the system that did it. (Owner: incident lead)
— ☐ Name the actions taken; attribute to the role/system, not the person's fault. (Owner: incident lead)

Stage 2 — Cause
— ☐ Ask "what made the wrong action easy?" five times. (Owner: incident lead)
— ☐ Stop at a missing control, not a missing hero. (Owner: incident lead)

Stage 3 — Fix
— ☐ Every action item has one owner and a due date. (Owner: incident lead)

Owner: incident lead. Trigger: incident over 15 min. Done-when: causes are systems, fixes are owned.

Save this. Run it every time.