Use 'how did this happen' not 'why did you do this' in postmortems
In technical postmortems, use 'how' questions ('how did the deployment occur') rather than 'why' questions ('why did you skip review') because 'how' elicits description while 'why' elicits defensive justification.
Why This Is a Rule
"Why did you skip the review?" activates defense: the person now needs to justify their decision rather than describe what happened. The answer will be shaped to minimize blame — omitting details, reframing the sequence, emphasizing external pressures — because the question implicitly assigns fault through the word "why" combined with a personal subject ("you").
"How did the deployment occur?" activates description: the person walks through the sequence of events as they unfolded, including details they might not have shared if they were defending a decision. "How" questions request process reconstruction; "why" questions request justification. The same information surfaces, but the descriptive version is more complete and more accurate because it's not filtered through defensive self-presentation.
This is foundational to blameless postmortem practice: the goal is to understand the system that produced the failure, not to identify the person who made the mistake. "How" questions investigate the system; "why" questions investigate the person.
When This Fires
- Conducting incident postmortems or failure analyses
- Investigating any system failure where human actions were involved
- During retrospectives when discussing what went wrong
- Any investigation where accurate description is more valuable than justified explanation
Common Failure Mode
Using "how" with an accusatory tone: "How could this possibly have gotten through?" This smuggles "why" into "how" — the question is really "justify this failure." Genuine "how" questions are neutral and process-focused: "How did the change move from development to production? What steps did it go through?" The tone must match the word.
The Protocol
In postmortems: (1) Replace every "why" question with a "how" question. "Why did you deploy without testing?" → "How did the deployment proceed? What steps occurred between code completion and production?" (2) Keep the subject focused on the process, not the person: "How did the system allow this?" not "How could you have allowed this?" (3) Follow the description with curiosity, not judgment: "What happened next?" until the full sequence is reconstructed. The descriptive account, unfiltered by defense, is where the systemic insights live.