Ask 'what was the system state' not 'who caused this' in postmortems

Why This Is a Rule

"Who caused this?" produces defensive silence. "What was the system state at 14:30?" produces descriptive information. The difference is grammatical — subject and verb — but the downstream effect on information quality is enormous. "Who" questions assign agency and implicitly assign blame; "what" questions request system state descriptions that include the same information without the blame frame.

"What information was available to the person making the decision?" is particularly powerful because it reconstructs the decision context. Hindsight makes every incident look like obvious negligence. But the person deploying at 14:30 didn't have the dashboard view from 15:00 showing the error spike. They had the information that was available at 14:30, which told a different story. Reconstructing the available-information state produces genuine understanding of why reasonable people made the decision they did — which is where systemic fixes live.

Blameless doesn't mean no one was involved. It means the investigation focuses on system state and information availability rather than on individual fault. The same facts surface, but the framing produces collaboration instead of defense.

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.