"I don't want the details": why good postmortems change systems, not people

After a minor incident escalated to an SVP call, engineer Michael Heap was cut off mid-explanation with “I don’t want the details.” What sounded dismissive turned out to be a statement of trust: the executive already assumed everyone had acted competently and reasonably, so rehashing the causal chain would only produce empathy — and empathy, once granted, quietly removes the pressure to change anything. The only question that mattered was what would be different next time.

Heap’s argument is that most organizations ask “why did this happen?” and mistake a convincing timeline for a fix. A tidy explanation where no one is at fault feels like closure, but it guarantees the same failure recurs months later. The better framing treats reasonable people producing a bad outcome as the baseline and asks what in the system needs to change — unambiguous ownership when someone’s on holiday, a defined path for late requirement changes, better alert signal-to-noise. Corrective actions that depend on people “being more careful” or remembering a conversation aren’t fixes; they’re organizational folklore that would evaporate if the team turned over.

The test he proposes is whether the same situation tomorrow would actually play out differently, and whether the fix would survive everyone involved leaving. He also warns against overcorrecting: not every failure warrants new process, and consciously accepting a risk with eyes open is legitimate — as long as it’s a deliberate decision rather than a group agreement to try harder. For anyone running incident reviews or SRE culture, it’s a concise reframing of blameless postmortems around durable systemic change instead of understanding for its own sake.