A decision failed.
The numbers are disappointing.
The expected result never arrived.
The project did not work.
The investment of time and resources produced less than expected.
So was the decision wrong?
Not necessarily.
Sometimes a bad outcome comes from a bad decision.
Sometimes a good decision produces a bad outcome.
And sometimes the answer sits somewhere in between.
This distinction matters because businesses can learn the wrong lesson from their own history.
A leader can make a sensible decision with the information available at the time and still experience an unexpected outcome. Conversely, a decision can produce a successful result while being based on weak reasoning.
If a business judges every decision purely by its outcome, it risks confusing luck with judgement.
The better question is:
“Was the decision reasonable given what we knew at the time?”
A Good Decision Can Produce a Bad Outcome
Imagine a business is considering whether to launch a new product.
The leadership team researches customer demand, studies the market, estimates costs and considers several possible scenarios.
The available evidence supports launching.
The business proceeds.
Then something unexpected happens.
A major competitor releases a similar product.
Customer demand changes.
A supplier experiences an unexpected disruption.
The product fails to achieve the expected result.
Looking backwards, the decision may appear obviously wrong.
But hindsight changes the picture.
The leadership team did not have access to information that became available later.
That matters.
A decision should not automatically be considered poor simply because the eventual outcome was disappointing.
A Bad Decision Can Produce a Good Outcome
The reverse is also true.
Imagine a business makes a decision based on a weak assumption.
The reasoning is poor.
The risks are not properly examined.
The leadership team gets lucky.
A competitor unexpectedly exits the market.
Demand increases.
A new customer arrives.
The business makes a substantial return.
Was the decision good?
The result was good.
The decision may not have been.
This is one of the most important distinctions in business thinking.
Outcome quality and decision quality are not identical.
A successful result can reinforce poor thinking if people assume:
“It worked, therefore we made the right decision.”
That can be dangerous.
The business may repeat the same reasoning in a completely different situation where luck does not protect it.
Hindsight Makes Everything Look Easier
Once the outcome is known, uncertainty disappears from the story.
Before the decision:
“We think this could happen.”
After the decision:
“This is what happened.”
That difference is enormous.
Once people know the result, the path to that result can seem obvious.
A failed product looks like a mistake.
A successful expansion looks like good judgement.
A missed opportunity looks like something leadership should have anticipated.
But the people making the decision did not have the benefit of knowing the future.
This is why hindsight can distort how organisations evaluate their own decisions.
The question should not simply be:
“Did it work?”
It should also be:
“What did we reasonably know when we decided?”
Separate the Decision From the Outcome
A useful way to think about this is to separate four things:
Decision
What did we choose to do?
Information
What did we know when we made the choice?
Assumptions
What did we believe would happen?
Outcome
What actually happened?
These four things should not be collapsed into one.
A business can have:
Good information + sensible assumptions + reasonable decision + bad outcome
Or:
Weak information + poor assumptions + questionable decision + good outcome
The final result alone cannot tell you which one occurred.
So What Does a Good Decision Look Like?
There is no universal formula for a good decision.
But a reasonable decision-making process often involves several elements.
The decision-maker understands the objective.
The important assumptions are visible.
Relevant information has been considered.
Alternative options have been examined.
Major risks are understood.
Uncertainty is acknowledged.
The consequences of being wrong have been considered.
And there is some basis for believing the chosen option is appropriate.
None of this guarantees success.
That is the point.
Good decision making is about improving the quality of the reasoning before the outcome is known.
What Were the Odds at the Time?
One useful question is:
“Given what we knew then, what outcomes were reasonably possible?”
This changes the evaluation.
Suppose a company enters a new market with incomplete information.
The leadership team knows the market is uncertain.
It identifies several possible outcomes.
It creates conditions under which the expansion will be reviewed.
The market eventually performs badly.
The decision may still have been reasonable.
Compare that with a company that enters the same market without researching demand, ignores obvious warning signs and assumes success is guaranteed.
Both companies could lose money.
But the quality of their decisions may be very different.
The outcome alone does not reveal the difference.
Look at the Process, Not Just the Result
When reviewing an unsuccessful decision, ask:
What did we know?
What did we not know?
What assumptions did we make?
What alternatives did we consider?
What risks did we identify?
What risks did we overlook?
What information became available later?
These questions help separate bad judgement from bad luck.
They also create a better learning environment.
Instead of simply saying:
“The decision failed.”
the business can ask:
“Which part of our reasoning failed?”
That is a much more useful question.
Luck Has a Bigger Role Than Businesses Sometimes Admit
Business outcomes contain uncertainty.
Two companies can make similar decisions with similar levels of preparation and experience different results because circumstances outside their control differ.
A customer may leave.
A competitor may change strategy.
Regulations may change.
Technology may develop unexpectedly.
A supplier may fail.
A market may move in an unexpected direction.
These events do not automatically prove that management made a poor decision.
They may simply show that the future cannot be controlled completely.
The existence of uncertainty does not mean decisions are random.
It means decision quality has to be evaluated without pretending that leaders control every variable.
But “It Was Just Bad Luck” Can Also Become an Excuse
There is a danger on the other side.
A business can use luck as a convenient explanation for every failure.
“It was the market.”
“The timing was unlucky.”
“The customer changed their mind.”
“We could not have known.”
Sometimes those explanations are valid.
Sometimes they are not.
The important question is whether the event was genuinely outside reasonable consideration.
Perhaps there were warning signs.
Perhaps customers had already shown weak interest.
Perhaps the forecast relied on an assumption nobody tested.
Perhaps the team ignored an alternative explanation because it preferred the original story.
If those factors existed, calling the outcome “bad luck” may prevent the business from learning the real lesson.
What Was Knowable?
This may be the most useful question in the entire discussion.
Not:
“What do we know now?”
But:
“What could we reasonably have known then?”
That distinction protects a business from hindsight bias while still allowing it to identify genuine mistakes.
Suppose a product failed because customer demand suddenly collapsed after a major external event.
If there was no reasonable way to anticipate that event, the failure may not tell us much about the quality of the original decision.
But suppose customer research had already shown weak demand and the leadership team ignored it.
That is different.
The information existed.
The organisation simply did not give it enough weight.
What Would Have Changed the Decision?
Another useful test is:
“What information, if known at the time, would have changed our decision?”
If the answer is something that was genuinely unknowable, the outcome may have been driven largely by uncertainty.
If the answer is information that was already available but ignored, the organisation may have a decision-making problem.
This question also helps identify future improvements.
Perhaps the business needs better research.
Perhaps it needs stronger challenge from other team members.
Perhaps assumptions need to be documented.
Perhaps decision-makers need to distinguish evidence from opinion more carefully.
The point is not to find someone to blame.
It is to identify what should change.
The Counterfactual Test
A useful exercise is to imagine going back to the moment before the decision.
You know everything that was actually known at that point.
You do not know what happened afterwards.
Now ask:
Would we make the same decision again?
If the answer is yes, that may indicate the original decision was reasonable even though the outcome was poor.
If the answer is no, ask why.
Was there information that should have been given more weight?
Was an assumption weak?
Was an alternative ignored?
Was the risk underestimated?
Was the decision influenced by emotion, pressure or organisational politics?
This exercise forces the review back into the conditions that actually existed when the decision was made.
Keep a Decision Record
For important decisions, a simple written record can be surprisingly useful.
Before making the decision, record:
- the decision being considered
- the objective
- the key assumptions
- the evidence supporting those assumptions
- the main alternatives
- the major risks
- what would make the team reconsider
- what outcomes are expected
Then review the decision later.
This creates a record of what the business actually believed before the result was known.
Without that record, hindsight can quietly rewrite history.
People may remember the decision differently.
They may remember themselves as more certain than they actually were.
They may forget the assumptions that seemed reasonable at the time.
A decision record gives the organisation something more reliable to learn from.
Do Not Reward Luck as if It Were Skill
This is particularly important for leaders.
If someone makes a poor decision and happens to get a good outcome, the organisation should be careful about treating the result as proof of excellent judgement.
Otherwise, luck can become reinforced as strategy.
A leader makes a risky decision.
It works.
The business celebrates.
The leader becomes more confident.
The next decision is even more aggressive.
Eventually, the same reasoning encounters an environment where luck does not intervene.
The problem was not that the first outcome was good.
The problem was the lesson taken from it.
Do Not Punish Good Judgement for a Bad Outcome
The opposite mistake can be equally damaging.
If employees are punished every time a reasonable decision produces a poor result, they may become excessively cautious.
People stop experimenting.
They delay decisions.
They seek unnecessary approval.
They avoid responsibility.
A business can therefore create a culture where the safest decision is simply to make no decision.
That is not good decision making either.
A healthy organisation needs room for reasonable decisions to fail without automatically treating the decision-maker as incompetent.
Measure Decision Quality Before the Outcome
A useful leadership habit is to evaluate decisions at two different points.
Before the outcome
Ask:
Was the reasoning sound?
Were the assumptions visible?
Was the evidence sufficient?
Were alternatives considered?
Were major risks understood?
After the outcome
Ask:
What happened?
Why did it happen?
What was predictable?
What was genuinely unexpected?
What should we change next time?
This creates a distinction between decision evaluation and outcome evaluation.
Both matter.
They simply answer different questions.
The Goal Is Better Learning, Not Perfect Hindsight
Businesses cannot remove uncertainty.
They cannot guarantee that every reasonable decision will succeed.
And they cannot predict every external event.
What they can do is improve how they learn.
A failed decision should create questions.
A successful decision should create questions too.
Why did it work?
Which assumptions were correct?
How much of the result came from our actions?
How much came from circumstances?
Would the same approach work again?
Those questions prevent success from becoming overconfidence and failure from becoming unnecessary blame.
The Bigger Lesson
A bad outcome is not automatically evidence of a bad decision.
And a good outcome is not automatically evidence of a good decision.
The difference lies in the quality of the reasoning, the information available at the time, the assumptions being made and the risks that could reasonably have been considered.
This is especially important for capable leaders.
If every failure is labelled poor judgement, people learn to fear decisions.
If every success is labelled good judgement, people learn to trust luck.
Neither creates better thinking.
The better approach is to examine the decision under the conditions that actually existed when it was made.
Ask:
What did we know?
What did we assume?
What could we reasonably have known?
What happened that we could not have anticipated?
And most importantly:
What should we learn from this without rewriting history?
Takeaway
A business decision should not be judged solely by its outcome.
A good decision can produce a bad result because of uncertainty, timing or events outside the decision-maker’s control. A poor decision can produce a good result because circumstances happened to work in its favour.
The real lesson comes from separating decision quality from outcome quality.
When a decision fails, examine what was knowable at the time.
When a decision succeeds, examine how much of the result came from judgement and how much came from circumstances.
Good business thinking is not about pretending luck does not exist. It is about making sure luck does not get mistaken for judgement.
Frequently Asked Questions
How can you tell if a business decision was wrong?
Review the decision using the information and circumstances that were available when it was made. Examine the assumptions, evidence, alternatives and risks rather than judging the decision only by its eventual outcome.
Can a good business decision have a bad outcome?
Yes. Uncertainty means that a reasonable decision can produce an unexpected or disappointing result. The quality of the decision should be evaluated separately from the outcome.
Can a bad decision have a good outcome?
Yes. A decision based on weak reasoning can sometimes succeed because circumstances happen to favour it. A successful outcome does not automatically prove that the decision-making process was sound.
Why is hindsight dangerous when reviewing decisions?
Once the outcome is known, events can appear more predictable than they actually were. Hindsight can cause businesses to judge earlier decisions using information that was unavailable when those decisions were made.
What is the best question to ask after a failed decision?
A useful question is:
“Knowing only what we knew at the time, would we make the same decision again?”
That helps separate genuine decision-making problems from outcomes driven by uncertainty or unexpected events.
