Mistakes reveal the gap between expectation and reality. Great leaders use them to improve systems, grow teams, and accelerate learning — rather than assigning blame.
Fail faster is catchy. It is also incomplete.
There's a phrase that echoes around conference halls, social feeds, and the slide decks of companies trying to sound braver than they are.
Fail faster.
It is catchy. It is energetic. And on its own, it is incomplete.
Not all failures are equal. Some are lessons. Some are scars. A few are earthquakes. The difference between them isn't the fact of failure — it's what happens in the gap that failure opens up.
Every mistake is a gap. The gap between what you expected to happen and what actually happened. And inside that gap sits something valuable: evidence, insight, clarity. But only if anyone looks.
Whether you use what's in the gap — or sweep the mistake aside and close it — is what separates teams that compound into something over time from teams that spend a decade re-learning the same three lessons.
Editor's note — where this sits
This essay sits in the Flywheel layer of the Idea to Value system — the layer concerned with how small, consistent actions compound into lasting capability. It treats mistakes not as personal shortcomings but as systemic signals — and the response to them as the practice that determines whether an organisation learns or merely moves.
The Idea to Value system — five layers
The gap between expectation and reality
Early in my career, I started using the 5 Whys technique — asking why repeatedly until the root cause surfaced.
We ran hundreds of them in one startup. Not because we were incompetent, but because we were relentlessly curious. Every breakdown was treated as data. The real value wasn't just identifying the cause. It was discovering how we could have prevented it, detected it earlier, or designed the system differently.
Growth is a creative endeavour. Creative work involves risk. Risk produces mistakes. Mistakes are part of a striving organisation, and part of being human.
The absence of mistakes is rarely excellence. More often, it is paralysis dressed up as professionalism — an organisation too afraid of being wrong to put anything meaningful at stake. The question isn't whether mistakes will happen in a working organisation. They will. The question is what the organisation does with them when they do.
Most mistakes are systemic
People rarely want to make mistakes. Most of us dislike them deeply. So why do they happen?
Workload overwhelms attention. Instructions are unclear. Tools and systems are missing or broken. Expectations are misaligned. Feedback loops are absent. Stress and distraction degrade judgement.
These are rarely individual shortcomings. They are system design challenges.
As a manager, mistakes in your team are signals about the system people are part of — not character judgements about the people themselves. The instinct to locate fault in a person is almost always the lazy version of the harder work of locating it in the system. The system is where the leverage is. The system is where the improvement lives.
How leaders should respond
When a mistake surfaces: gather facts. Understand context. Contain the impact. Communicate clearly.
Do not humiliate. Do not panic. Do not perform blame.
Then learn — and improve the system so the same gap cannot open again.
A simple rule: respond to others' mistakes the way you would want your manager to respond to yours.
The wiser default, almost always, is curiosity rather than control. What actually happened? Why did it happen? What can we improve? Not: Who is at fault? Who should be embarrassed?
This matters because mistakes tend to produce a predictable organisational response: control increases. More approvals. More gates. More oversight. Sometimes that is necessary. Often, it is fear disguised as governance — process added not because it will prevent the next mistake but because it will make someone feel like action has been taken.
Process can prevent catastrophe. It can also suffocate learning. Knowing which one is happening in a given moment is part of the work of leadership.
Mistakes are data, patterns are signals
There's a useful three-step calibration for how to read mistakes:
- The first is learning.
- The second is a warning.
- The third is a pattern.
Patterns require systemic change — training, guidance, tooling, workflow redesign, clearer ownership. Individual mistakes don't. The confusion between these two categories is where most organisational overreaction comes from. A single mistake gets treated like a pattern, which produces the process cascade that kills experimentation. A genuine pattern gets treated like a single mistake, which produces the quiet repetition of the same failure over and over.
Make it safe to surface mistakes early. Fear hides information. Hidden information compounds cost.
Creativity and innovation require a safe climate. When fear dominates, experimentation dies. And innovation without the possibility of failure is not innovation — it is performance. Nice words. Empty platitudes. The organisation that claims to want innovation while punishing its precursors is asking for an impossible thing, and usually gets exactly what it deserves.
Match responsibility to experience
Not all mistakes are equal, and not all responsibilities are. Responsibility must match capability.
A new hire should not run live systems alone. Someone unfamiliar with a process should not make irreversible decisions without support.
Create safe sandboxes for learning. Let people stretch without breaking the organisation, or themselves. This is not coddling — it is the structural recognition that learning requires room to fail safely, and that removing all possibility of failure also removes all possibility of real learning.
There is a balance to hold here. We don't want reckless mistakes that damage people or organisations. Boundaries matter. Safety matters. Care matters. But within those boundaries, learning must be allowed to breathe.
Ownership is leadership
Mistakes in your team belong to you.
You hired them. You trained them. You shaped the environment they operate in.
Great managers don't punish people for mistakes — they ensure learning happens, and improve the system continuously. This is exhausting work. And it is the work of leadership.
A team that feels safe to surface mistakes early is a team that learns faster than its competitors. A team that feels safe to experiment is a team that grows faster than its competitors. The two are the same property of the same climate, and both compound over time.
Mistakes are not the enemy. Wasted human potential is. And learning is what converts mistakes into progress.
Failure, when studied, becomes refinement. Refinement, repeated, becomes mastery.
Not failure as identity. Failure as information.
Go deeper
This principle is one of 26 in the full deep dive Idea to Value system. Here's where to continue.
Watch the full Studio session below
4.5 hours of practitioner-level video across all 26 principles — separate from the course, and going significantly deeper. Built for people who want to go deep and apply the system with a rich understanding.
Get the Idea to Value course
The complete field guide and video series — all 26 principles explained clearly, with practical examples and a way of seeing your work you won't be able to unsee. The clearest place to get the full system in one place.
Start with the Orientation Session
A free 21-minute overview of how ideas move from concept to value — the clearest place to begin with an overview of the full system. Free on signup.
All three are designed to help you not just understand the system — but use it. Not sure where to start? Begin here →
This post is for paying subscribers only
Subscribe now and have access to all our stories, enjoy exclusive content and stay up to date with constant updates.
Already a member? Sign in