Evaluate decisions by process, not outcome

Judge a decision by the quality of the reasoning at the time, not by what happened.

Why it works

Outcome bias — a close cousin of hindsight bias — causes people to rate the same decision as good or bad depending purely on whether it worked, even when the decision process was identical. This creates perverse learning: lucky decisions get reinforced, unlucky good ones get punished, and neither lesson reflects how to actually decide well under uncertainty.

How to do it

1. After any significant outcome, explicitly reconstruct: what information was available at decision time?
2. Ask whether the reasoning process was sound given that information — not whether it produced a good result.
3. Separate the verdict on the decision from the verdict on the outcome; record both.
4. Reinforce good process even when outcomes are bad, and scrutinize good outcomes for lucky-process errors.

Evidence

Research on outcome bias shows that people reliably judge the same decision-process more harshly when it leads to a bad outcome, even when the decision was identical. This is well established in lab settings. (observational)

Lab demonstrations are robust; changing real-world evaluation practices in organizations is harder and less studied. People who learn about outcome bias still exhibit it when judging their own decisions.

Sources

• Baron & Hershey (1988), "Outcome bias in decision evaluation", Journal of Personality and Social Psychology

Common mistake

Assuming that a good outcome proves the decision was good — this is the most common way hindsight and outcome bias compound. The result can be confidence built on luck.