There is a leadership habit that quietly damages teams every day.
Something goes wrong. A deadline is missed. A client gets the wrong information. A handover doesn’t happen. A decision creates chaos weeks later. And almost instantly, the room starts looking for the person who dropped the ball.
Who missed it?
Who owns this?
Who made the mistake?
The real problem isn’t where we usually look
On the surface, that feels efficient. Find the problem. Fix the person. Move on.
But that is rarely what is really going on. In modern workplaces, mistakes do not usually happen in isolation. They happen inside busy, fast-moving environments where people are juggling competing priorities, clunky processes, unclear expectations, fragmented communication, rushed decisions, and constant change. In other words: they happen inside a system.
And that is the bigger issue many organisations still avoid. We talk about performance as though it lives entirely inside the individual, while ignoring the environment around them. Then we wonder why capable people keep making avoidable errors, why accountability feels shaky, and why managers are exhausted.
This is where leadership has to mature.
Because if you are leading in a system under pressure, your job is not just to manage people. Your job is to read the patterns, inspect the conditions, and strengthen the layers around performance.
That is a very different leadership task.
When the holes line up
One of the most useful ways to understand how mistakes happen is through what is often called the Swiss cheese phenomenon: each layer of a team’s work system is like a slice of Swiss cheese, with small holes or vulnerabilities in it. Most of the time, those holes do not line up. But when they do, the error passes through every layer and turns into a visible failure.
Think about the slices: process, communication, capability, decision-making, leadership oversight, timing, pressure, or workload. On their own, none of those gaps may be catastrophic. A slightly unclear brief is manageable. A rushed meeting is survivable. One unchecked assumption is not usually fatal. A “good enough” handover may pass. A team member carrying too much might still hold things together.
But when several of those gaps line up at once, that is when something slips through.
That is when the client gets the wrong message.
That is when the project derails.
That is when the wrong decision gets implemented.
That is when a safety issue appears.
That is when trust takes a hit.
This is why blame is often such a poor diagnosis. It focuses on the final hole, the one we can see, instead of the stack that allowed the problem through. And that matters because if leaders only fix the visible last step, they leave the rest of the system untouched. Which means the same pattern is still there, waiting for a new person, a new deadline, or a new pressure point to trigger it again.
What one famous breakdown can teach us
The Mars Climate Orbiter failure in 1999 makes the point perfectly: one team used imperial units, another used metric, and the breakdown happened because the system around the work did not catch the mismatch. It is a powerful reminder that when things go wrong in organisations, the real issue is often not the last person who touched it, but the conditions that allowed the problem to travel all the way through.
A familiar pattern in the real world
I was called into a retail business because head office believed stores had a productivity problem. The assumption was that store managers and staff were not executing well enough. But when I spent time on the ground with front-of-house teams, a different picture emerged. What we found was Swiss cheese in the system: misalignment between head office and stores, miscommunication on priorities, missed delivery deadlines, late changes, understaffing, and unclear ownership when things went wrong.
Once we mapped it out, the issue was clear. This was not one person or one team underperforming. It was a series of small breakdowns lining up at the same time and making productive work far harder than it needed to be. So the answer was not to push harder on store teams. It was to fix the system around them.
How to diagnose the system, not just the symptom
Here is a practical way to look at it. When a mistake happens, inspect the system through four layers:
This is where your wider systems lens matters. From an integral perspective, breakdowns do not just sit in one quadrant of organisational life. They can show up in the individual, in relationships, in structures, and in culture. That is why single-point fixes so often disappoint. If the problem is systemic, the solution has to be broader than “try harder”.
So the leadership move is this:
Do not just inspect behaviour. Inspect behaviour, relationships, process, and context. That is how you find the real leverage.
Practical steps for any project or team leaders:
1. Replace blame with diagnosis
When something goes wrong, resist the rush to personalise it. Start with: What conditions allowed this to happen?
2. Review the full chain
Look at the layers, not just the last visible error. Process, communication, capability, leadership conditions.
3. Find the recurring holes
Was this a one-off, or does the same kind of breakdown keep showing up in different forms?
4. Patch the system, not just the incident
Clarify decision rights. Improve handovers. Add checkpoints. Reduce ambiguity. Tighten priorities. Remove friction.
5. Build a culture where people can surface misses early
If your team is afraid to flag errors, risks, or uncertainty, you are effectively asking problems to stay hidden until they become expensive.
6. Teach leaders to see systemically
This is where L&D has a real role to play. Not just building individual capability, but helping leaders understand how culture, structure, behaviour, and pressure interact.
Because the truth is, most organisations do not need more finger-pointing. They need better pattern recognition.
If this resonates, take one recent mistake, miss, or frustration in your team and ask a different question: What lined up in the system to make that outcome possible? That one question will tell you far more than another conversation about who dropped the ball.