Ask 'what was the system state' not 'who caused this'…
In blameless postmortems, frame questions as 'what was the system state at [time]' and 'what information was available' rather than 'who caused this' to shift from evaluation to observation and enable information sharing.
When This Fires
- Conducting blameless postmortems after incidents
- Investigating process failures where multiple people were involved
- Running retrospectives where defensiveness has been a problem
- Any investigation where accurate information is more valuable than assigned blame
Common Failure Mode
Using blameless language while asking blame-shaped questions: "Can someone explain what happened with the deployment?" This is blame by indirection — everyone knows who "someone" is. Genuinely blameless questions are impersonal and system-focused: "What was the deployment pipeline state at [time]?" "What monitoring signals were visible between [time] and [time]?"
The Protocol
In postmortems: (1) Replace every "who" with "what" or "how." "Who approved this?" → "What was the approval status at the time of deployment?" (2) Add temporal specificity: "What was the system state at [specific time]?" (3) Reconstruct information availability: "What information was available to the decision-maker at [time]?" This question alone transforms the investigation from blame to understanding. (4) The systemic question: "What about the system's design made this outcome possible?" This is where the fix lives — not in individual behavior, but in system architecture.