Knowing how it ended makes an investigator misjudge a decision that was reasonable at the time
Aliases: hindsight bias · accident investigation · outcome bias
What it is
By the time an accident is investigated, the investigator already knows the outcome — and that knowledge systematically distorts how the person's decisions at the time get judged. This distortion is called hindsight bias. Knowing the outcome makes it easy for an investigator to redescribe a judgment that was reasonable, even optimal, given the information available at the time, as an error that "should have been obvious" — as if the person should have foreseen a consequence that only became clear afterward. This bias isn't investigators being deliberately unfair; knowing the outcome makes the causal chain look, in retrospect, clearer and more inevitable than it actually was as it unfolded.
Why it happens
Hindsight bias comes from how people reconstruct events in memory: information gained afterward gets unconsciously folded into the estimate of an earlier state, producing an illusion that "the outcome was already fixed, and the process was always headed there." When an investigator, already knowing this decision led to a bad outcome, asks the person "why did you judge it that way at the time," the question's framing already presumes it was a wrong judgment. Under that framing, it's hard for the person to give a complete account of the information they actually had, the time pressure they were under, and the alternatives available to them — they tend to unconsciously drift toward explaining "yes, I got it wrong" rather than reconstructing the real decision situation of incomplete information and limited options. The result is that what ends up recorded in the investigation report is often not "what could be seen at the time" but "what looks missed in hindsight," and conflating the two turns systemic causes into what looks like personal misjudgment.
Studying it
A classic way to test how hindsight bias shapes judgment of an accident has two groups of raters read the exact same record of a decision process; one group is told in advance whether the outcome was good or bad, the other isn't, and the study compares how the two groups rate whether the decision was reasonable at the time. The group that knows the outcome typically rates it noticeably more negatively, even though the decision-process record they read is identical. Methodological caveat: this line of research demonstrates that the bias exists and which direction it runs, but it's hard to derive a general "bias correction factor" from it, since the size of the bias is moderated by how ambiguous the situation was and how severe the outcome turned out to be. Investigative practice can't simply apply a fixed discount to compensate; it needs to actively block the bias at the level of process design instead.
Where it stops holding
Acknowledging hindsight bias doesn't mean the decision at the time was necessarily reasonable — some decisions really were clear misjudgments given the information available then. The way to tell the difference is to re-evaluate strictly anchored to the information the person actually had access to at the time, rather than excusing every decision wholesale. This boundary also doesn't apply when the person concealed or misrepresented information they actually held at the time — if evidence shows they knowingly ignored a key piece of information, that goes beyond what hindsight bias can explain and moves into a discussion of violation or deliberate negligence.
Applying it
When interviewing the person involved, explicitly ask them to describe "what was actually showing on your screen, in the materials in front of you, at that moment" rather than "where do you think, looking back now, your judgment went wrong." The first question anchors to the information state at the moment of the event; the second directly invites them to re-judge the past using an outcome they now know. The two questions produce information of very different quality. Investigation records should keep separate columns for "information available to the person at the time" and "the full picture known afterward," presented side by side rather than blended together — any conclusion that only holds up in the "known afterward" column should never be written as a judgment of the person. Verification: audit the wording of an investigation report for phrases like "should have caught this," "obviously," or "should have foreseen," and check whether the information the person actually had access to at that moment really contained a cue that would support that judgment. If it turns out that information wasn't available at the time, the report has already been contaminated by hindsight bias.
Related
- Same group: A10.16.2 a single root-cause conclusion usually masks several jointly contributing factors · A10.16.3 timely error reporting depends on report cost being low enough and decoupled from punishment · A10.16.4 the point of an investigation is to find improvable system conditions, not to pin down who to blame
- Nearby: A10.07 Swiss cheese model · A10.09 human reliability and blame culture
- Search terms:
hindsight bias·accident investigation·outcome bias