Stephen T’s Blog Spot

After a program fails, the review almost writes itself. The warning signs were there all along. The decision looks negligent. Surely someone should have seen it coming. The trouble is that most of this clarity is manufactured. It appears only after you learn the outcome, and it quietly rewrites your memory of how uncertain things really were at the time.

Psychologists call this hindsight bias, or creeping determinism. In a classic 1975 study, Baruch Fischhoff showed that once people are told how an event turned out, they raise their estimate of how predictable it had been, and they misremember their own earlier guesses as closer to the truth. Knowing the ending makes the whole story feel inevitable. People given the outcome inflated the probability they claimed they would have assigned beforehand, by a meaningful margin.

There is a closely related trap. We judge the quality of a decision by how it turned out, rather than by what was known when it was made. Jonathan Baron and John Hershey demonstrated in 1988 that the same choice is rated as wise when it ends well and foolish when it ends badly, even when people are told the available information was identical and are instructed to ignore the result. A sound bet that loses still gets graded as a bad bet. The name for this one is outcome bias.

This is an occupational hazard for anyone who evaluates programs and decisions after the fact, which is most of us. With the outcome in hand, a failed initiative looks obviously doomed and its leaders careless, while a success looks inevitable and its strategy brilliant. Both readings are distorted by the same mechanism. We end up praising luck and punishing sound judgment that happened to draw a bad card.

The damage runs deeper than unfair reviews. We learn the wrong lessons. If every bad outcome is treated as a bad decision, we teach people to avoid reasonable risks and to manage appearances instead of making good calls. We also miss the dangerous cases, the good outcomes that came from poor reasoning and simple luck, which are exactly the ones likely to fail next time. Hindsight does not just misjudge the past. It corrupts what we carry forward.

The fixes have to be deliberate, because the bias is automatic. Judge the decision by what was knowable at the time, and reconstruct the information and constraints the decision-makers actually faced. Hold apart two questions that hindsight fuses: was this a good decision, and did it turn out well? They are not the same. Where you can, write down predictions and reasoning before the outcome is known, so you are not rebuilding them later through the fog of the result. And use the debiasing move with the best evidence behind it: deliberately ask how things could have gone differently, and why a careful person might have chosen as they did.

For those of us in evaluation, lessons-learned reviews and after-action reports are where this bias does its quietest work. The disciplined approach is to reconstruct the decision as it looked going in, to credit sound process even when results disappointed, and to resist the satisfying story in which everything that happened was always going to happen. The aim is to learn what was actually learnable, not to enjoy the false comfort of a tidy, inevitable past.

So here is my question: When you review a project that went badly, do you separate the quality of the decision from the quality of the outcome, or does the result color the whole assessment?