What is outcome bias?
Outcome bias is the tendency to judge the quality of a decision by how it turned out, rather than by the information and reasoning available when the decision was made.
Definition
Outcome bias is the tendency to judge the quality of a decision by how it turned out, rather than by the information and reasoning available when the decision was made.
Psychologists Jonathan Baron and John Hershey named the effect in 1988. In their experiments, people rated identical decisions as better or worse depending only on whether the result was good or bad — even when they were told the decision-maker could not have known the result in advance.
The bias matters because it corrupts learning. If results decide who was right, you end up copying luck and punishing sound judgement.
Outcome bias vs hindsight bias
The two are related but not the same. Hindsight bias, documented by Baruch Fischhoff in 1975, is the sense that an outcome was predictable all along once you know it happened — a distortion of memory and probability.
Outcome bias is a distortion of evaluation: even people who accept that the result was genuinely uncertain still grade the decision by the result.
- Hindsight bias: "I knew it would happen."
- Outcome bias: "It happened, so the choice was wrong."
Examples
The pattern repeats anywhere results arrive later than decisions.
- Investing: a concentrated bet pays off, so the investor is called disciplined rather than lucky — and the position size is never questioned.
- Hiring: a strong hire underperforms after a reorganisation, so the interview process gets rebuilt even though it worked as designed.
- Shipping: a rushed launch happens to land well, so skipping review becomes the new standard until the first time it does not.
How to avoid outcome bias
You cannot switch the bias off, but you can separate the decision from the result before the result exists.
- Write the decision down first: what you expected, what you were uncertain about, and what would change your mind. Judge the decision later against that record, not against the outcome.
- Review the process, not the score. Ask whether the reasoning would still be defensible if the same choice had produced the opposite result.
- Run a pre-mortem. Before committing, describe how this fails, so a bad result later is recognised as a known risk rather than a verdict on your judgement.
- Separate luck from skill explicitly. For every good result, ask which part you controlled.
Why this blog is called Outcome Bias
The name is a deliberate inversion. The bias is judging decisions by results; the practice worth building is being biased toward outcomes that matter while still grading your own thinking honestly.
That tension runs through everything published here — AI leverage, clear thinking, and operating systems that compound instead of merely looking busy.
Frequently asked questions
What is outcome bias?
Outcome bias is judging a decision by its result instead of by the information and reasoning available at the time it was made. A well-reasoned decision with an unlucky result gets rated as a bad decision.
What is an example of outcome bias?
A surgeon recommends an operation with strong odds of success. The patient has a rare complication. Reviewers who know the complication rate the same recommendation as reckless, even though nothing about the decision changed.
What is the difference between outcome bias and hindsight bias?
Hindsight bias is believing an outcome was predictable once you know it happened. Outcome bias is evaluating the decision itself by that outcome, even while accepting that it was genuinely uncertain beforehand.
How can you avoid outcome bias?
Record decisions before results arrive, including what you expected and what would change your mind. Review the reasoning rather than the score, run a pre-mortem, and name which part of any result you actually controlled.
Why is outcome bias a problem for founders and operators?
It teaches the wrong lessons at scale. Teams copy processes that happened to work once and abandon sound processes after a single bad quarter, which makes decision quality drift with luck.