Exercise 3: Why Blameless Postmortems Produce Better Data Over Time — Possible Solution
====================================================================

The counterintuitive part, acknowledged directly: identifying who made
a specific mistake FEELS like it should lead to accountability and
therefore better outcomes. In practice, per the chapter, the opposite
tends to happen.

Why blame backfires, mechanism by mechanism:

1. IT DISCOURAGES HONEST REPORTING. If people know that admitting "I
   made this change" or "I missed this in review" during a postmortem
   could result in personal blame or consequences, they have a direct
   incentive to be LESS forthcoming with exactly the details a
   postmortem needs to be useful -- downplaying their own role,
   omitting details, or framing events in a way that minimizes their
   personal exposure rather than maximizing the accuracy of the
   account.

2. IT SHIFTS FOCUS AWAY FROM THE ACTUAL FIXABLE PROBLEM. Per the
   chapter's own 5-Whys example (Chapter 5), the genuine root cause of
   an incident is very often a PROCESS OR SYSTEM GAP -- "code review
   didn't catch it because there's no automated test for connection
   cleanup" -- not simply "a person made an error." Humans making
   occasional mistakes is essentially inevitable in any system;
   focusing blame on the individual who happened to trigger a given
   incident does nothing to prevent the NEXT person from making a
   similar mistake, since the underlying gap (missing test coverage,
   in this example) remains completely unaddressed.

3. IT UNDERMINES FUTURE POSTMORTEMS SPECIFICALLY. If a blame-focused
   postmortem culture develops, people may become reluctant to fully
   participate in or contribute honestly to FUTURE postmortems too --
   not just for this one incident -- degrading the quality of incident
   data across the organization over time, not just for a single case.

Why blameless culture produces BETTER data:

Per the chapter, a blameless approach focuses on "what allowed the
failure to happen (process or system gaps)" -- this framing makes it
psychologically safer for people to report honestly what actually
happened, including their own role in it, because the postmortem's
goal is explicitly understood as fixing the SYSTEM, not assigning
personal consequences. More honest, more complete accounts directly
translate into better-informed root cause analysis and genuinely more
effective action items (Chapter 5/6's material) -- which is the
concrete, practical payoff of what initially feels like a
counterintuitive choice to not name names.

WHY THIS WORKS AS AN ANSWER
------------------------------
This explains the actual causal mechanism -- blame changes people's
incentive to report honestly, which directly degrades data quality --
rather than simply asserting "blameless is nicer." It also connects
directly to Chapter 5's own 5-Whys example, showing that the genuine
root cause the chapter cares about (a process gap) is a different kind
of thing entirely from "a person's mistake," which is exactly why
focusing on the person misses the actual, fixable target.