John Gall’s The Systems Bible: The Beginner’s Guide to Systems Large and Small is a satirical masterpiece on the dysfunctions of systems. Gall’s “General Systemantics” offers brilliant, if painfully accurate, observations about how systems in organizations often fail, not because they’re poorly designed, but because they operate within a flawed human context. The core irony is that no matter how well-crafted a system may be, it will inevitably behave in unexpected, often irrational ways once it encounters the realities of human interaction.
One of Gall’s most famous insights is that “A complex system that works is invariably found to have evolved from a simple system that worked.” This notion crashes headlong into the reality of large organizations, where systems are anything but simple. Bureaucracies are built on complexity—intricate structures where accountability is fragmented, decision-making is diffused, and the primary mode of operation is survival rather than innovation. The result is an organization where the only thing that thrives is political maneuvering, not system improvement.
In such environments, the lofty principles of The Systems Bible—which often feel like warnings against exactly this type of scenario—become almost prophetic. Gall’s Laws, like “Systems tend to oppose their own proper function,” seem to play out daily. In complex organizations, even the simplest attempt to improve a system is likely to be blocked, delayed, or diluted by endless layers of approval, resistance from territorial departments, and the overriding focus on maintaining the status quo.
The ultimate irony? Despite having The Systems Bible as a guide, with its incisive breakdown of how systems should work and why they fail, no one can do much to fix anything. Political games dominate, and people spend more time managing relationships and navigating the internal power structure than implementing changes. Improvements that could streamline operations or increase efficiency get lost in the bureaucracy. The system is built to resist change—even when there’s a clear understanding of how it’s failing.
Gall’s work is full of wisdom about how systems, large and small, are prone to dysfunction. In complex organizations, however, this wisdom becomes a kind of tragicomedy: we know why systems fail, but the people who could change them are too entrenched in political survival to act. The result is a self-perpetuating cycle where everyone acknowledges the problems, yet no one has the power—or the incentive—to do anything about them.
Gall’s Most Damning Observations
The Fundamental Law: Complex Systems Evolve, They Don’t Get Built
One of Gall’s most profound insights is the distinction between building and evolving. “A complex system that works is invariably found to have evolved from a simple system that worked.” The corollary—often overlooked—is equally devastating: “A complex system designed from scratch never works, and cannot be patched up to make it work.” This directly contradicts the prevailing wisdom in large organizations, where the standard response to problems is to add more layers, more processes, and more complexity.
Bureaucracies operate on the assumption that complexity equals sophistication. In reality, it often just means dysfunction layered upon dysfunction, with each new layer adding its own political considerations and territorial concerns.
Systems Oppose Their Own Function
Another cornerstone of Gall’s philosophy is that “Systems tend to oppose their own proper function.” In complex organizations, this manifests constantly:
- The HR system meant to attract talent becomes a resume-screening bottleneck
- The approval workflow designed for quality control becomes an innovation killer
- The communication platform built to collaborate becomes information noise
- The metrics system designed to measure success becomes a game to be gamed
The system, once established, develops its own organism-like drive toward self-preservation—often directly opposing the purpose it was created to serve.
The Law of Conservation
Gall observes that “Complicated systems require a large administrative staff.” The tragedy: once created, this staff works primarily to ensure its own continued existence. The finance department doesn’t streamline to become unnecessary; it grows to justify its existence. The compliance team doesn’t simplify regulations; it interprets them in increasingly labyrinthine ways.
In complex organizations, the bureaucratic immune system is far stronger than the immune system against actual dysfunction.
Deliberate Dysfunction as Stability
Perhaps most troubling is Gall’s insight that “Systems tend to maintain their own dysfunction.” Not accidentally—deliberately. In large organizations, change threatens established power structures. Those who have built careers within the current system have no incentive to fix it. The very inefficiencies that plague the organization are often the same inefficiencies that allow certain power centers to maintain control.
Reform doesn’t just fail; it’s actively resisted by those with the power to implement it.
Why Understanding Gall’s Laws Doesn’t Help
In such environments, the principles of The Systems Bible—which feel like prophetic warnings—become almost useless. Consider the situation:
Political Survival Over System Improvement: Even the simplest attempt to improve a system faces endless layers of approval, resistance from territorial departments, and focus on maintaining status quo. Everyone knows the system is broken. Fixing it would disrupt established relationships and threaten career investments.
Knowledge Without Power: The cruel irony is that despite having The Systems Bible as a guide—with its incisive breakdown of how systems should work and why they fail—no one can do much to fix anything. Managers read Gall’s insights at lunch and recognize themselves in the examples. Then they spend the afternoon navigating the very dysfunctions he described. The wisdom is freely available. The ability to act on it is not.
Self-Perpetuating Cycles: The system is built to resist change—even when failure is obvious and acknowledged. Improvements get lost in bureaucracy. Data showing inefficiency gets buried in reports. The person who spots the problem knows reporting it could make them a target. The person in charge of fixing it has too much invested in status quo. Nothing changes.
The Real Issue: It’s Not About Systems, It’s About Power
Organizations don’t fail because nobody understands the problems. They fail because understanding and power are divorced. Consider:
- Understanding doesn’t imply power - The individual contributor who sees the flaw may lack any authority to fix it
- Authority doesn’t require understanding - The executive with power to change things may not want to see the problems
- Change is a threat - To someone’s territory, someone’s budget, someone’s influence, someone’s identity
- Systems are for people, by people - And humans are driven by self-interest, fear, and desire for control more than optimization
Finding Small Ways Forward
Given this bleak landscape, Gall does offer a few constructive insights:
Start simple: When building systems, begin as simple as possible. Many organizations fail because they tried to construct the complete bureaucracy day one instead of letting it evolve naturally from basic foundations.
Accept constraints: Some dysfunctions in large systems aren’t bugs—they’re features. They exist because they solve someone’s problem, even if they create problems for everyone else. Recognizing this saves you from futile crusades.
Work within the system: The futility of top-down reform is nearly complete. But small, localized improvements that don’t threaten existing structures can sometimes propagate. Think evolution, not revolution.
Distinguish symptoms from causes: Organizations excel at treating symptoms because treating actual causes would require confronting those who benefit from the status quo.
The Tragic Insight
The true irony of The Systems Bible in complex organizations isn’t that Gall was wrong. It’s that he was exactly right, and that rightness is almost completely useless in practice.
We have a detailed map of organizational dysfunction. We understand the laws that govern it. We can predict failures with uncanny accuracy. And yet we remain trapped within systems that we understand are broken, managed by people who understand they’re broken, serving purposes increasingly divorced from the actual mission.
The systems we create to solve problems become problems themselves. The people who could fix them are too busy surviving within them. The knowledge to understand dysfunction doesn’t translate to power to fix it. And the people with power to fix it benefit from the dysfunction remaining as it is.
The real message of Gall’s work isn’t prescriptive—”here’s how to fix systems.” It’s descriptive—”here’s why your systems are broken, and here’s why that’s probably never going to change.”
And somehow, knowing that deeply and truly—rather than just intellectually—is simultaneously liberating and depressing. Liberating because it frees you from the fantasy that better systems are just a memo away. Depressing because it confirms what you already suspected: in complex organizations, we’re not trying to fix systems. We’re trying to survive them.