Gall's Law
Why complexity must evolve from what already works
In short
Gall's Law is a systems theory principle stating that any complex working system has evolved from a simple working system. Attempting to design a complex system from scratch almost always results in failure. To build durable complex structures, design must proceed incrementally from a proven, simple core.
When organizations and projects face large-scale challenges, the temptation to engineer comprehensive, grand solutions is strong. Yet experience across IT, governance, and medicine demonstrates that monolithic approaches frequently collapse. Physician and systems theorist John Gall formulated the core dynamics behind this pattern: functional complexity cannot be commanded into existence from scratch, but must be earned through step-by-step adaptation.
Background and Theoretical Formulation
John Gall, an American pediatrician and systems theorist, published the book Systemantics in 1975. In it, he formulated an observation that has become a cornerstone of systems theory: a complex system that works is invariably found to have evolved from a simple system that worked. Gall added an equally critical corollary: a complex system designed from scratch never works and cannot be patched up to function properly. When a grand construction crashes, it happens because hidden flaws and unmonitored interactions become too numerous to manage. The only viable path forward is to scale down, isolate the smallest functioning core, and build upon it incrementally.
Why Grand Blueprint Designs Fail
The reason grand blueprint designs fail lies in the human mind's limited capacity to anticipate all prospective interactions within a dynamic environment. When a system is theoretically designed with hundreds of interconnected components, the plan implicitly assumes that the surrounding environment will remain static and predictable. In reality, unnoticed feedback loops, unexpected bottlenecks, and changing user needs constantly emerge. If the system has not been hardened incrementally within a real operational context, these latent tensions trigger simultaneously upon launch, resulting in catastrophic failure rather than minor operational friction.
Limits of the Principle and Common Planning Pitfalls
When large-scale projects fail, organizations frequently react by demanding even more detailed upfront planning and specification documents for their next attempt. Gall's Law demonstrates that additional theoretical planning of an unproven complex system rarely solves the underlying problem, often increasing the risk of miscalculation instead. At the same time, certain domains—such as constructing bridges or nuclear reactors—do demand extensive physical pre-planning. Yet even in those contexts, the law holds true at the component level: every subsystem and safety valve must be tested and validated in its simplest form before being integrated into the larger whole. This aligns closely with findings from [brooks-lag-fordjupning](brooks-lag-fordjupning) and [hofstadters-lag-fordjupning](hofstadters-lag-fordjupning).
Sources
Read also
Reflection exercises
Use these exercises to apply the chapter's ideas. You don't need to write anything down — just pause and reflect on each question.
Strip Down to the Working Core
Identify a complex project or system around you that feels sluggish or overloaded.
- What is the smallest functioning component of this project that delivers actual value today?
- How could you strip away secondary complexity and stabilize the simple core first?
Summary
Gall's Law clarifies that there are no shortcuts to functional complexity. Complex systems that work are always rooted in simple systems that first proved their viability in practice. By establishing a solid baseline and expanding iteratively based on feedback, systemic failures are minimized.
Read the short version in the archive.