A business launches a new service.

Before the launch, the team conducts customer interviews, reviews the available evidence, examines the financial risks and tests the offer through a small pilot. Demand appears credible. The required investment is affordable and the plan includes clear review points.

Then an unexpected economic shock affects the sector. Several prospective customers delay spending, a partner withdraws and the service fails to reach its revenue target.

The organisation concludes that launching it was a bad decision.

Elsewhere, another business introduces a product after minimal research. The founder ignores concerns from the team, makes optimistic assumptions about demand and commits more money than the organisation can safely afford.

A competitor unexpectedly leaves the market. Media attention follows, customers arrive and the product becomes profitable.

The founder is praised for making a brilliant decision.

The first organisation used a responsible process and experienced a poor outcome. The second used a weak process and received a favourable one.

If both businesses judge themselves only by what happened, they will learn the wrong lessons.

Outcomes contain more than decisions

A decision influences an outcome, but it does not control it.

Results are also shaped by execution, timing, customer behaviour, competitor activity, economic conditions, regulation, technology, institutional power, cultural response and chance.

This is especially important when decisions are made under uncertainty.

A founder may examine the evidence and reasonably conclude that a new offer has potential. The offer can still fail because market conditions change.

A leader may make a poorly examined acquisition that later produces a financial return because an unexpected event increases the value of the acquired assets.

A cultural organisation may design a thoughtful programme that does not meet its attendance target because transport disruption prevents people from reaching the venue.

A campaign may receive extraordinary attention because an influential person shares it at the right moment.

The quality of the decision and the quality of the outcome are related, but they are not identical.

Good decision-making improves the probability of favourable results. It does not guarantee them.

Poor decision-making increases exposure to avoidable risk. It does not ensure immediate failure.

This distinction can be difficult to accept because businesses prefer simple stories. Success is attributed to talent. Failure is attributed to error. A complicated result becomes a clean lesson.

But a clean lesson is not always an accurate one.

The outcome changes how the past looks

Once people know what happened, the earlier uncertainty becomes difficult to remember.

A failed initiative begins to look as though it was always destined to fail. Warning signs that received limited attention at the time now appear obvious. People remember their doubts more clearly and become less able to recall the evidence that supported proceeding.

After success, the opposite happens. Risks appear smaller than they originally were. Lucky events become part of a story about strategic foresight. People remember supporting the decision more strongly than they actually did.

The outcome rewrites the past.

This produces hindsight bias: the tendency to see an event as more predictable after it has occurred.

It appears in statements such as:

We should have known.

The opportunity was obvious.

There was no way that strategy could work.

Everybody could see where the market was heading.

I knew this would happen.

Sometimes people genuinely did identify the eventual result as a possibility. But recognising one possibility is not the same as knowing it would occur.

A useful review asks what information was available when the decision was made—not what became visible afterwards.

What did the team know?

What remained uncertain?

Which outcomes were considered plausible?

What evidence supported the chosen option?

What risks were recognised?

What could not reasonably have been predicted?

Without that reconstruction, organisations judge earlier decisions using knowledge that did not exist at the time.

A successful decision may still have been reckless

Success can protect a bad process from scrutiny.

A founder may commit nearly all the organisation’s available cash to an untested idea. If the idea succeeds, the risk is forgotten and the founder’s confidence is celebrated.

The organisation may then repeat the same behaviour on a larger scale.

What appears to be a lesson in bold leadership may actually be the beginning of a dangerous habit.

A favourable outcome should therefore be reviewed with the same seriousness as a failure.

Ask:

Did the decision rely on credible evidence?

Were the most important assumptions identified?

Was the level of risk proportionate?

Were alternative options considered?

Could the organisation have survived an unfavourable result?

Did the outcome depend on an event that was not part of the original reasoning?

Would we make the same decision again under similar conditions?

Success can result from strong judgement. It can also result from luck, privileged access, temporary conditions or risks that happened not to materialise.

This does not mean the achievement should be dismissed. It means the organisation should understand what produced it.

If a business attributes every successful outcome to skill, it may become increasingly confident while the quality of its decision-making declines.

A failed decision may still have been responsible

Failure does not automatically prove that proceeding was wrong.

Suppose an organisation identifies an opportunity with a reasonable probability of success. The potential benefits are substantial, the downside is limited and the organisation can afford the experiment.

It runs a controlled pilot.

The pilot does not work.

If the decision was made responsibly, the failure may still produce useful information. The organisation has learned something about the audience, proposition, price, timing or delivery model without exposing itself to unacceptable harm.

That is different from launching carelessly.

Responsible decisions under uncertainty are not defined by whether every initiative succeeds. They are defined by whether the organisation:

used the best relevant information available;

distinguished evidence from assumption;

considered credible alternatives;

assessed the possible consequences;

limited avoidable exposure;

created opportunities to learn;

remained willing to change direction.

An organisation that punishes every unsuccessful experiment will eventually discourage honest experimentation.

People will choose only safe projects, conceal uncertainty or redefine objectives after the event to make results appear favourable.

The challenge is to distinguish intelligent risk from preventable carelessness.

Failure should not receive automatic praise simply because it produced learning. Learning does not justify every cost. But neither should every disappointing result be treated as proof of incompetence.

Separate the decision from the execution

A sound decision can be undermined by weak execution.

The organisation may have selected the right audience but communicated the offer poorly. The strategy may have been reasonable, but responsibilities were unclear. The product may have solved a genuine problem, but customers encountered delays or an inaccessible purchasing process.

Equally, strong execution can temporarily support a weak decision. A highly capable team may work around problems in the original strategy, creating the appearance that the decision itself was sound.

A proper review separates at least four questions:

Was the decision process sound?

Did the organisation use relevant evidence, examine assumptions, consider alternatives and assess risk?

Was the chosen strategy reasonable?

Given what was known, did the selected option offer an acceptable relationship between potential value and possible harm?

Was the strategy executed effectively?

Were responsibilities, resources, timing, communication and delivery managed well?

What external factors affected the outcome?

Which events were outside the organisation’s direct control, and how much influence did they have?

These questions stop every problem from being blamed on “the strategy” and prevent weak strategies from being protected by exceptional effort.

They also lead to more useful action.

If the problem was the decision process, improve how choices are made.

If the strategy was wrong, revisit the underlying assumptions.

If execution was weak, address capability, coordination or resources.

If an external event changed the conditions, consider whether the strategy should be adapted rather than abandoned.

Do not use uncertainty to avoid accountability

The role of chance does not remove responsibility.

Leaders cannot excuse every poor result by saying that the future was uncertain. Some risks are foreseeable. Some evidence is ignored. Some failures follow from unrealistic forecasts, inadequate preparation or decisions made beyond the organisation’s capacity.

A decision can be criticised fairly when:

important evidence was available but disregarded;

obvious conflicts of interest were not addressed;

the organisation concealed or minimised serious risks;

affected people were excluded from the process;

the potential harm was disproportionate to the expected benefit;

there was no credible plan for execution;

leaders continued after evidence weakened the original case;

the decision exceeded an agreed risk limit without justification.

Accountability should focus on what people could reasonably have known and controlled.

This produces a more demanding standard than simply blaming whoever was closest to a bad result. It asks whether the organisation exercised appropriate care before and during the decision.

Critical thinking is not a method for explaining away failure. It is a method for locating responsibility more accurately.

Record the decision before the outcome rewrites it

One of the simplest ways to improve organisational learning is to create a decision record before the result is known.

For significant decisions, record:

The decision: What has been agreed?

The objective: What is the decision intended to achieve?

The available evidence: What information supports it?

The principal assumptions: What must be true for the plan to work?

The alternatives: What other options were considered?

The uncertainties: What is not currently known?

The risks: What could go wrong, and with what consequences?

The expected outcomes: What does the organisation think is likely to happen?

The confidence level: How strongly is the decision supported, and why?

The review triggers: What evidence or event will cause reconsideration?

The owner: Who is responsible for the decision and its implementation?

The review date: When will progress be examined?

The record should be short enough to use and detailed enough to preserve the original reasoning.

It should not become a document created only to defend leaders afterwards. Its purpose is to support learning and accountability.

Probabilities can also be useful.

Instead of stating, “The service will reach its target,” the team might record:

We believe there is approximately a 60% chance of reaching the six-month revenue target, provided two proposed partnerships become active.

The precise percentage may be imperfect. Its value lies in making uncertainty visible.

If the service misses the target, the record shows that failure was already considered possible. The review can then examine whether the estimated probability was reasonable and whether the required partnerships developed as expected.

Without a record, memory adjusts itself to fit the outcome.

Review the process and the result

A useful review examines the decision and the outcome on separate axes.

Good process, good outcome

The organisation used sound reasoning and achieved a favourable result.

The task is to identify what should be repeated without assuming every part of the outcome was produced by skill.

Good process, bad outcome

The organisation made a reasonable decision but experienced an unfavourable result.

The task is to understand what changed, what was learned and whether the process needs adjustment.

Poor process, good outcome

The organisation achieved a favourable result despite weak reasoning or excessive exposure.

This outcome requires particular care because success can reinforce dangerous behaviour.

Poor process, bad outcome

The decision process and outcome were both weak.

The task is to establish accountability, address the causes and improve the system rather than merely identifying somebody to blame.

The review should also distinguish leading indicators from final results.

Revenue may be the eventual objective, but early indicators could include qualified enquiries, conversion, repeat use, delivery cost or customer outcomes.

A programme may miss an attendance target while producing deeper participation and stronger partnerships than expected. That does not automatically make it successful, but it may reveal value that the original measurement failed to capture.

Good reviews do not move the goalposts to protect a preferred story. They examine whether the original measures were sufficient and what the complete result actually shows.

Reward honesty before certainty becomes hindsight

Organisations often say they value transparency but reward certainty.

A leader who confidently predicts success may receive more support than one who identifies genuine uncertainty. If the initiative later succeeds, the confident leader appears visionary. If it fails, the organisation may blame execution or changing conditions.

Meanwhile, someone who accurately described the uncertainty may be remembered as insufficiently committed.

This teaches people to conceal doubt.

A stronger culture rewards those who:

identify important assumptions;

communicate uncertainty clearly;

raise inconvenient evidence;

revise their view when conditions change;

distinguish what they know from what they believe;

record risks before they materialise;

stop or redesign work when the original case weakens.

These behaviours can feel slower in the moment. Over time, they improve the organisation’s ability to learn.

Leaders influence this culture through their response to unwelcome information.

If bad news produces blame, people delay reporting it. If changing one’s mind is treated as weakness, people defend positions beyond reason. If every failed pilot harms somebody’s reputation, experiments become symbolic performances designed to succeed.

Organisational learning depends on people being able to describe reality before reality becomes impossible to ignore.

Learn without pretending the future was obvious

After an outcome, the goal is not to produce a perfect explanation.

Business results often have multiple causes. Some will remain uncertain. Different people may reasonably interpret the same event in different ways.

The review should produce a more useful understanding, not a more confident story.

Ask:

What part of the outcome was influenced by the original decision?

What part resulted from execution?

What external events mattered?

Which assumptions were supported?

Which assumptions weakened?

What surprised us?

What information did we overlook?

What could not reasonably have been known?

What should we repeat?

What should we change?

What will we monitor differently next time?

Then turn the review into action.

Update the decision process. Revise a service. Change a threshold. Improve data collection. Clarify responsibility. Create a smaller pilot. Strengthen contingency planning. Stop work that is no longer justified.

Learning is not complete when the organisation holds a reflective meeting. It is complete when the next decision changes.

A mature business does not assume that every success proves its intelligence or that every failure exposes incompetence.

It understands that decisions are made in uncertainty, outcomes have multiple causes and responsibility must be assessed with care.

The purpose is not to protect people from consequences. It is to ensure that the right lessons are learned.

Judge the decision by the quality of the reasoning available at the time.

Judge the execution by how responsibly the plan was carried out.

Judge the outcome by what actually happened.

Then examine the relationship between all three.

A good decision can still produce a bad outcome. A bad decision can still be rewarded by luck.

The organisation that understands the difference is less likely to repeat its failures—or become dangerously confident because of its successes.