What If the System Is the Problem? Deming Was Right — And Here’s What Systems Leadership Looks Like
I want to tell you about a CEO I’ll call David.
David’s organization was struggling with five problems: declining engagement, widespread burnout, deepening silos, stalled strategy execution, and unclear accountability. Five problems that felt urgent, distinct, and overwhelming.
So David did what most conscientious leaders do. He attacked each one separately. He hired an engagement consultant. He rolled out a wellness program for burnout. He launched cross-functional task forces for silos. He brought in a strategy firm to redesign the strategic plan. He implemented a new performance management platform for accountability.
Five initiatives. Five consultants. Five budgets. Millions of dollars over three years.
Every metric got slightly worse.
It wasn’t that the consultants were bad or the programs were poorly designed. Each one, in isolation, was reasonable. The problem was that they were treating five symptoms as five separate diseases. The engagement consultant didn’t talk to the wellness consultant. The strategy firm didn’t coordinate with the performance management vendor. Each fix operated in its own lane, addressing its own slice of the problem, unaware that the other four slices were undermining its efforts.
Then David asked a different question. Not “How do we fix engagement?” or “How do we reduce burnout?” but: “What is the system producing, and why?”
That question changed everything. Instead of running five parallel initiatives, David’s team redesigned one operating architecture — the incentive structures, information flows, decision-making processes, and performance systems that connected everything. Within eighteen months, every metric improved. Not because they solved five problems. Because they solved one.
Deming Was Right. He’s Still Right.
W. Edwards Deming — the management thinker whose ideas transformed Japanese manufacturing and, eventually, global quality management — made a claim that seemed radical at the time:
“I should estimate that 94% belongs to the system. 6% special.”
Ninety-four percent of performance problems belong to the system. Not to the individuals working within it. Not to their motivation, their character, or their capability. To the structures, processes, incentives, information flows, and decision-making architectures that management designs and controls.
His point was that the vast majority of performance variation has nothing to do with individual workers. It is caused by the system in which those people operate.
When the system produces burnout, it’s not because people aren’t resilient enough. When the system produces silos, it’s not because people don’t want to collaborate. When the system produces unclear accountability, it’s not because leaders don’t value clarity. The system is producing exactly what it was designed to produce. If you don’t like the output, redesign the system.
This was a radical idea in Deming’s time. It should not still feel radical today. But in most organizations, it does. We continue to build leadership development programs that focus on individual capability while leaving the system untouched. We continue to hire new talent into broken structures and wonder why the outcomes don’t change. We continue to treat systemic failures as personal ones.
Ten Symptoms, One System
Consider the challenges facing leaders right now. Not as separate problems, but as connected symptoms of one operating system that was built for a different world:
Complexity is crushing leaders — the role has expanded dramatically without anything being subtracted. Burnout is organizational, not individual — it emerges from structural mismatches in workload, control, reward, and fairness. Nobody trusts the data because departments maintain separate systems with separate definitions. Strategy feels theoretical because execution systems weren’t designed for today’s pace and complexity. Results feel fragile because organizations optimized for short-term outputs at the expense of long-term capability.
Engagement keeps declining because the managers responsible for driving it are themselves unsupported and overwhelmed. Customers are angrier than leaders realize because perception gaps separate executive belief from customer reality. Silos are deepening because incentives and metrics reward departmental optimization over organizational outcomes. Accountability is unclear because commitments lack defined outcomes, named owners, and weekly rhythms.
These feel like nine different problems. They’re not. They are nine symptoms of one problem: the system.
Every one of these challenges traces back to structures, processes, incentives, and decision-making architectures that management designs and controls. And every effective solution requires changing the system, not just the people within it.
The playbooks and operating frameworks built for a stable, predictable, in-person world are now producing the very problems they were designed to solve.
The Three Capabilities of Systems Leaders
Peter Senge, who built on Deming’s work and developed the concept of the learning organization, identified three capabilities that leaders need to lead at the systems level. I’ve seen these three capabilities separate the leaders who genuinely transform organizations from the ones who keep running the same plays and wondering why the scores don’t change.
1. See the Larger System
Stop looking at engagement, burnout, silos, and accountability as separate problems. Start asking how structures, incentives, processes, and culture interact to produce the outcomes you observe.
This is perhaps the most important cognitive shift a leader can make. And it’s the one that most leadership development programs never teach. We train leaders to solve problems. We rarely train them to see the system that produces the problems.
The leader who sees these challenges as connected has an entirely different — and far more effective — set of responses available to them than the leader who sees nine isolated fires to fight. David spent three years and millions of dollars fighting individual fires. He made progress only when he stopped fighting fires and started examining the system that kept igniting them.
2. Foster Reflective Conversation
Every organization has undiscussable topics — system failures that everyone can see but nobody names. The strategy that isn’t working but can’t be questioned. The executive who creates silos but can’t be confronted. The performance metric that drives the wrong behavior but can’t be changed because someone powerful owns it.
Systems leaders create spaces where these undiscussable failures can be named, examined, and addressed without blame. Not because blame feels bad — though it does — but because blame stops the analysis. The moment we identify a person as the problem, we stop looking at the system. And the system is where 94% of the problem lives.
Reflective conversation isn’t therapy. It’s diagnostics. It’s the organizational equivalent of a doctor asking, “Where does it hurt and what makes it worse?” — without judgment, with genuine curiosity, in service of finding the actual cause.
3. Shift from Reactive to Co-Creative
Most organizations operate in reactive mode — putting out fires, responding to crises, fixing what broke last quarter. Systems leaders shift the organization toward deliberate redesign.
Not through a one-time reorganization. Those almost always fail because they replace one static structure with another static structure in a world that requires dynamic adaptation.
Instead: ninety-day pilots. Measured outcomes. Honest assessment. Iteration. Treat system redesign the way a scientist treats research — hypothesize, test, measure, learn, adjust. No single experiment will transform the organization. But a disciplined practice of experimentation, sustained over time, absolutely will.
David’s turnaround wasn’t a single dramatic reorganization. It was a series of deliberate, measured changes to the operating architecture — each one tested, assessed, and refined before scaling.
The Meta-Capability
If there is one idea I want to leave you with, it’s this: systems leadership is the meta-capability.
Every other leadership skill — communication, strategy, emotional intelligence, decision-making, coaching, accountability — operates within a system. If the system is broken, individual leadership excellence cannot overcome it.
A brilliant communicator in a siloed organization still can’t move information across boundaries. A masterful strategist in a system that rewards short-term thinking still can’t build long-term capability. A deeply empathetic leader in a system that produces burnout still watches people burn out.
The system is stronger than the individual. Always.
This doesn’t make individual leadership development unimportant. It makes it insufficient. The leaders who will define this era are the ones who develop both: the personal capability to lead well and the systems capability to redesign the structures that make leadership harder than it needs to be.
Where to Start
The playbooks built for a stable, predictable, in-person world are producing burnout, silos, disengagement, fragile results, and unclear accountability — not because the people are failing, but because the system was designed for a world that no longer exists.
The answer is not to push people harder within broken systems. The answer is to redesign the systems — with evidence, with courage, and with a commitment to treating organizational architecture as the leadership discipline it has always been.
Deming told us this decades ago. Senge refined it. The data confirms it every year.
Ninety-four percent belongs to the system.
The question isn’t whether to start. The question is where.
If you could redesign one part of your organization’s operating system tomorrow — the incentives, the information flows, the decision-making architecture, the performance structures — which one would have the greatest impact? And what’s stopping you from starting?
Sources
- W. Edwards Deming, Out of the Crisis and The New Economics (system variation theory; 94%/6% attribution)
- Peter Senge, The Fifth Discipline and “The Dawn of System Leadership” (learning organizations and systems leadership capabilities)
Gordon Klein is the founder of Reflect Excellence, a leadership and organizational performance consulting firm. He serves on the Sterling Council board and contributes to the design of Sterling’s Leadership Development curriculum. He works with organizations across sectors — healthcare, government, education, and business — on the systemic challenges that make leadership harder than it needs to be. Connect with him to continue the conversation.
