A good outcome is not proof of a good decision

Not every decision that ended well was a good decision, and not every decision that ended badly was a bad one.

This is outcome bias, and it can lead an organization to learn the wrong lesson.

We judge a decision by the result that followed it, rather than by the information and reasoning available when it was made.

A simple example

Management approves a major investment despite a weak business case, optimistic assumptions, and poorly assessed risks. Then the market unexpectedly improves, and the project delivers excellent profits.

The verdict? “It was a brilliant decision.”

Not necessarily. The decision may have been poor and luck rescued it. The reverse is also true: a decision can rest on sound analysis, reasonable assumptions, and measured risks, then be hurt by an unforeseeable external event. That does not make the decision itself bad.

The wrong lesson

So when reviewing any investment, pricing, expansion, or budget allocation decision, separate two questions:

1. Was the outcome good?
2. Was the decision itself good given the information available at the time?

They are two different questions.

The best defence: document the decision before the outcome

• What were the assumptions?
• What were the risks?
• What alternatives were considered?
• Why was this path chosen?

Once the outcome appears, revisit the record, not to decide who was right, but to ask whether the result came from a good decision or merely from good luck.

That is the difference between managing outcomes and managing decision quality.