How would you tell whether a team's postmortem process is genuinely blameless rather than blameless only on paper?

## Why you cannot read this off the policy Every engineering organisation with a wiki claims to run blameless postmortems. The claim is free. What a team actually believes is set by the most recent expensive incident: what happened to the person at the centre of it, and whether anyone paid a price for candour. So the question is empirical, and the evidence is behavioural. ## The signals worth trusting **People self-identify without being asked.** In a healthy review, the sentence "that was me, I ran it, here's what I was looking at" arrives early and casually. Where the culture is nominal, the timeline uses the passive voice throughout and nobody quite owns any action. Passive voice covering every consequential step is one of the most reliable smells in a draft. **The person closest to the action often writes the document.** This is a strong signal precisely because it is costly if the culture is fake. Where blame is real, that assignment is a punishment and everyone knows it. **Speed of raising a hand.** Fear shows up as latency. If people spend twenty minutes trying to quietly fix something before telling anyone, part of that delay is usually reluctance to attract attention. This is measurable — the gap between the first internal signal and the moment someone escalated — and it tends to shorten when candour stops being risky. **Small and near-miss events get written up.** A corpus containing only large, undeniable outages means the process is triggered by visibility rather than by learning. Voluntary write-ups of things that were caught in time are the clearest evidence that reporting feels safe. **Remediations point at systems.** Scan the action list. Items like "retrain the engineer", "add a reminder to the runbook", "remind the team to be careful" are blame laundered into process language: they name a person's future behaviour as the control. A healthy list is dominated by guardrails, defaults, detection and reversibility. **Language survives review.** Someone in the review actively strikes "should have", "failed to", "neglected to". If nobody ever edits for this, either the drafts are unusually good or nobody is reading them as a blameless document. ## The counter-signals **Blame that relocated rather than disappeared.** The document is scrupulously anonymous, and then the person's manager has a quiet word, or it surfaces at their next performance review. This is worse than open blame, because the team learns both that blame is real and that the process lies about it. **Attendance changes when the incident is expensive.** If a senior leader attends only the costly reviews and the room goes quiet when they do, the safety is conditional — and conditional safety is what you get during exactly the incidents that matter most. **Vagueness treated as kindness.** A document that avoids saying what actually happened, to protect someone, has sacrificed the learning to save the feelings. Blameless writing is more specific about actions and conditions, not less; it simply describes situations rather than character. **One-way flow.** Postmortems that are written but never read, never reviewed and never referenced in later work indicate a compliance ritual, whatever the tone of the language. ## Decisions that actually set the culture Three recurring choices, each with a real cost, do more than any statement of values: 1. **Do names appear in documents?** Naming with the person's consent normalises ownership when the culture is strong; enforced anonymity is the safer default when it is not — but anonymity chosen for safety should be understood as a symptom, not an achievement. 2. **How widely is the document published?** Org-wide publication maximises learning and raises the personal stakes. Many teams start narrow and widen as trust grows; the widening itself is a measurable milestone. 3. **Who is in the room, and what do they say first?** The single highest-leverage intervention is a senior person opening a review by describing their own past mistake. It costs them status and buys the room permission. ## What to say in an interview Avoid the trap of listing cultural virtues. Give the interviewer observable, ideally measurable evidence: who writes the document, whether small events appear at all, the shape of the remediation list, the latency before someone raises a hand, and the counter-signal of blame relocating into private conversations. Then name the intervention you would make first — usually funding the small write-ups and having a leader model self-disclosure — and be honest that the true test only arrives with the next expensive outage.