The System Is the Problem (But We Never Want to Admit It)
W. Edwards Deming once said, "A bad system will beat a good person every time."
It’s one of those quotes that sounds obvious until you start paying attention to how often organizations behave as if the opposite is true.
A deadline gets missed. A client is frustrated. A claim falls through the cracks. A project stalls. And somewhere in the meeting, someone says, "We just need more accountability."
What usually follows is a search for the person who dropped the ball.
Deming spent his career trying to convince leaders to ask a different question: why does the ball keep landing there?
Why Does the Ball Keep Landing There?
After World War II, Deming brought this argument to American executives. He told them something they did not' want to hear: most organizational failures were not employee failures at all. Quality problems weren't rooted in character. They were rooted in design. Broken workflows. Conflicting incentives. Unclear expectations. Fear-based leadership. These were management problems, not frontline character flaws.
America was not interested.
We were winning. Manufacturing was booming. It was much easier to believe success came from strong leadership and failure came from weak employees.
Japan listened instead. Japanese manufacturers took Deming's ideas seriously. They built systems around continuous improvement, process control, and the radical belief that quality should be designed into the work, not addressed at the end. They examined the structure around the work itself.
A few decades later, American executives were standing in parking lots staring at Toyotas and wondering what happened.
There is a business lesson there. But there is also an ethical one.
What does it mean to hold someone accountable for an outcome they were never structurally positioned to succeed in? To criticize a biller for denials created upstream by poor documentation? To demand innovation while making mistakes professionally expensive? To reward speed and then act surprised when quality declines?
Amy Edmondson adds another layer.
Her research on psychological safety challenged one of management's favorite assumptions: that high-performing teams make fewer mistakes.
They report more of them.
Not because they are less competent, but because people feel safe enough to surface problems before those problems become expensive. In unhealthy systems, mistakes are hidden because information is dangerous. In healthy systems, information moves.
People know the difference instinctively. They know when raising a concern will be seen as helpful and when it will be seen as disloyalty. They know when ownership means empowerment and when it means being handed a mess with no authority to fix it.
Eventually, they adjust.
They stop raising concerns. They protect themselves instead of the mission. They learn that silence is safer than truth.
Leadership calls that disengagement. Edmondson would call it predictable.
Peter Senge pushed the thinking even further.
He noticed that most organizations are obsessed with events. The missed deadline. The lost client. The resignation. Events are loud. They get attention.
But events are rarely the real problem. They are symptoms.
Beneath the event is a pattern. Beneath the pattern is a structure. And beneath the structure are the assumptions people carry about how work is supposed to happen.
This is where many leaders lose patience.
It feels productive to solve the event. Correct the employee. Rewrite the policy. Move on. It is much harder to ask what pattern keeps recreating the same fire. Why does every new hire struggle at the same handoff? Why do the same client frustrations appear across departments? Why does the same type of error survive training, meetings, and consequences?
That question forces leaders to look at the architecture. And architecture is slower work than blame.
Blame is efficient. It gives us a villain. It creates the illusion of control. It protects leadership from admitting that sometimes the problem is not the person inside the machine. Sometimes it is the machine.
And lately, many organizations are drifting further from Deming, not closer. You can see it in the headlines. Companies celebrate relentless performance while employees describe systems built on fear and exhaustion. The language is modern, but the philosophy is old: push people harder and outcomes will improve.
Sometimes they do. For a while.
But fear suppresses bad news. It discourages creativity. It teaches people that self-protection matters more than truth. It is efficient in the short term and expensive in the long term.
Deming would not be surprised.
Here is what we’re learning lately at Wayfinder:
When the same problem shows up repeatedly, it is almost never a coincidence.
If ten people struggle in the same role, it is probably not ten separate failures. If every department complains about the same handoff, it is probably not a personality issue. If the same mistake keeps happening despite training and consequences, the system is telling you something.
The question is whether you are willing to listen.
Most companies say they want accountability. Often what they want is speed. A fast answer. A clean culprit. A reason that does not require rethinking the architecture.
"Who dropped the ball?" is easier.
"Why does the ball keep getting dropped here?" is transformative.
If you’re looking for a starting point, pick one recurring frustration in your work. Just one. The denial that keeps reappearing. The handoff everyone complains about. The employee turnover in the same role. The meeting where people always leave confused.
Then sit with it longer than feels comfortable.
Ask yourself:
Is this truly a performance issue, or a design issue?
If three different people struggle in the same place, what does that suggest about the structure around the work?
What behavior is the system actually rewarding, regardless of what leadership says it values?
Where does information get stuck because telling the truth feels expensive?
If someone on your team knew exactly why this keeps happening, would they feel safe enough to say it?
And the hardest one: What part of this problem benefits the person asking the question? Because sometimes issues persist not because no one sees them, but because solving them would require someone with power to change.
This is where the real work begins.
Not in fixing people. In examining the environment people are being asked to succeed inside.
Patterns are not accidents. They are messages. Are we brave enough to listen?
