Most organisations are better at explaining a failure than learning from it.

A project misses its deadline. A forecast proves too optimistic. A customer leaves for reasons that, with hindsight, appear obvious. The leadership team meets to understand what happened.

The discussion is thorough. The contributing factors are identified. Responsibilities are clarified and actions agreed. Everyone leaves with the reassuring sense that the problem has been dealt with.

Then, months later, the same failure returns wearing different clothes.

It may involve another project, another customer or another part of the business. The details have changed, but the organisation has once again trusted an assumption it did not test, ignored a warning it did not want to hear or continued for too long because stopping had become difficult to justify.

The previous failure was discussed. It may even have been documented. But nothing important changed in the way the next decision was made.

The comfort of a good explanation

When something goes wrong, leaders naturally want to make sense of it. A coherent explanation restores order. It tells us why the outcome occurred, what was outside our control and what should now be done.

That is useful. It can also bring the conversation to a close before the organisation has learned anything.

A review can concentrate on the circumstances surrounding a decision while leaving the thinking inside it untouched. The market changed. The information arrived late. The team did not execute as expected. Communication should have been clearer.

Any of those explanations may be accurate. Yet none necessarily asks the more uncomfortable question:

What did we believe that turned out not to be true?

Perhaps we believed the customer valued a feature they barely used. Perhaps we assumed silence meant agreement. Perhaps we believed an experienced person would ask for help before a problem became serious. Perhaps we took continued investment as evidence that the original decision remained sound.

These beliefs matter because they did more than contribute to the explanation afterwards. They shaped what people noticed, which questions they asked and how long they continued.

When a review becomes a defence

There is another reason the underlying belief can survive the review.

A disappointing result rarely feels like a neutral piece of information when you were responsible for the decision. It can feel like evidence about your judgement, competence or authority. The conversation may be intended to examine what happened, while part of you is quietly working to ensure it does not become a verdict on you.

In my Leading Unmasked approach, I call this automatic response the Mask. It is the familiar pattern that takes over when something feels psychologically dangerous. It generates thoughts and responses intended to prevent other people, and often us, from seeing what it already fears might be true: “I am not enough.”

In a review, the Mask does not necessarily deny the failure or avoid responsibility. Its influence can be much more convincing than that. It helps us construct an account in which our original judgement remains fundamentally sound.

We acted reasonably on the information available. The conditions were unusual. Nobody could have anticipated what followed.

Again, this may all be true. But if the purpose of the conversation quietly shifts from improving future judgement to establishing that the past judgement was defensible, the team can leave with an excellent explanation and an unchanged decision-making system.

Discussion is not the same as learning

Research suggests that properly conducted debriefs can materially improve performance. A meta-analysis involving 46 samples and 2,136 participants found an average improvement of approximately 20 to 25 per cent. But the researchers made an important distinction: an effective debrief is developmental rather than punitive, examines a specific event, uses more than one source of information and requires participants to engage actively in discovering what should change.

Read the research on effective debriefs.

A meeting called a review does not automatically produce learning. Neither does a long action list. Reassigning a task, tightening a deadline or requesting another report may address part of the previous failure without improving the judgement that precedes the next one.

Organisational learning becomes visible only when experience changes a future decision.

Change the next decision

The next time a consequential piece of work falls short, resist the pressure to end the review once the causes make sense. Stay with the decision long enough to ask two questions:

What did we believe that turned out not to be true?

What will change the next time that belief shapes a decision?

The answer needs to alter something concrete. It might change the evidence required before proceeding, the point at which a concern must be escalated, the person whose perspective enters the room or the conditions that would cause the team to stop.

Suppose a leadership team concludes that a project failed because risks were reported too late. “Improve communication” is an understandable response. But it leaves the deeper assumption intact: that people will recognise when a concern has become important enough to raise.

Learning might mean agreeing specific warning indicators that trigger a review, regardless of whether the project lead believes the problem is under control. That change reaches forward into the next decision. It reduces the organisation’s dependence on individual confidence and judgement.

The same principle applies personally. If your own decision went wrong, the useful question is not only whether you can explain it. It is whether you can identify the assumption you were protecting, and allow the experience to revise it.

The real test

Leaders understandably want their organisations to move on from failure. Endless examination can become another form of avoidance. But moving on and learning are not opposites. Proper learning makes it possible to move on without carrying the same mistake into a new set of circumstances.

The test is simple. Look at the next comparable decision.

Did the team require different evidence? Did somebody ask a better question? Was a warning treated differently? Did the leader become less invested in proving the original judgement correct?

If the next decision is made in essentially the same way, the lesson was not learned. It was only discussed.

Until next week,

Gavin