Gall's Law

Gall's Law

Every complex system that works grew out of a simple system that worked. Gall’s Law says build small, get it working, then grow it, because designing complexity from scratch rarely succeeds.

Want something complicated that actually works? Gall’s Law says build a simple version that works first, then improve and expand it step by step. Try to build the full, complicated version in one go and it will almost always fail.

Start Small, Then Grow

  • Building a house🏠 Nobody starts with a mansion. You build something small, like a single room or a cabin, and once you know it stands, you add rooms, floors and finishing touches. Attempt the whole mansion at once without testing anything and it might come down around you.

  • Apps or software📱 Successful apps usually begin as a small minimum viable product (MVP). Facebook, for example, started as a simple site just for Harvard students. Only once that worked did it grow into the giant platform it is today.

  • Airplanes✈️ The Wright brothers didn’t start with a jumbo jet. They built a simple glider, learned from it, moved on to powered planes, and aviation gradually evolved into modern airliners.

👉 The idea: Start small, make sure it works, then grow.

Gall's Law is widely quoted by engineers and product people, and it often rings true. But it comes from a satirical book, not a body of research, and its absolute wording invites some pushback.

  1. It's an aphorism, not a findingJohn Gall's Systemantics, first published in the mid-1970s, is a deliberately tongue-in-cheek guide to how systems fail, and reviewers at the time praised it for its wit as much as its insight. The law distils hard-won experience, but nobody has systematically tested it. Its support is mostly anecdote: the failed big rewrite, the successful product that started small.

  2. "Invariably" and "never" are doing a lot of work: Gall says a complex system designed from scratch never works and can't be patched into working. That's a strong universal claim, and the vague key terms make it hard to check. What counts as "simple"? What counts as "working"? Almost any successful system can be retold as having grown from some earlier working thing, which makes the law hard to falsify.

  3. Grown systems carry their historyEvolution, the law's favourite analogy, also shows the downside of building only on what already works. Each step must function, so early compromises get locked in. Software that grows organically can likewise end up as a "big ball of mud": it works, but it's tangled and hard to change. Starting simple is not a guarantee of a good end state.

  4. It's easy to agree with and hard to applyPractitioners note that teams often accept the principle, then keep enlarging the "minimum" version until it is the complex system again. The law tells you to start simple but says little about how simple, or how to plan the path from the small core to the big goal.

None of this makes Gall's Law bad advice. As a heuristic for building software, products and organisations, especially in unpredictable conditions (the "complex" domain of the Cynefin framework), it's one of the more reliable rules of thumb around. Just treat it as distilled experience, not a law of nature.

Resources

Gall’s Lawstates: A complex system that works is invariably found to have evolved from a simple system that worked.

John Gall's dry one-liner, from his 1975 book Systemantics, applies to working systems everywhere: in engineering, in biology, in organizations. Successful complexity is grown step by step. It doesn't arrive whole from a top-down blueprint.

Connections to Other Principles

  • Evolutionary Biology (Darwin’s Principle)🧬 Organisms evolve gradually from simpler forms, and successful systems likewise adapt over time. Designing a fully formed "complex organism" from scratch is unrealistic.

    • ExampleThe human eye evolved through many intermediate stages, each of them functional on its own.
  • Software Engineering (YAGNI & MVP)💻 In Agile development, the Minimum Viable Product (MVP) is Gall’s Law in action: build the smallest thing that works, then iterate. You Aren’t Gonna Need It (YAGNI) adds the warning not to build complex features before you need them.

  • Systems Theory🔄 Complex adaptive systems such as ecosystems and economies can only emerge from simpler, stable components. (The Cynefin framework makes a similar point: in complex situations you probe with small experiments rather than design the answer up front.) Trying to design that complexity directly tends to produce fragility or outright failure.

  • Cybernetics & Control Theory⚙️ Stable control systems (thermostats, autopilots) start life as basic feedback loops. Bolting on complexity before stability is proven usually destabilizes the whole thing.

  • Conway’s Law🏢 Systems mirror the structure of the organizations that design them. As organizations grow organically, their systems grow more complex in step, echoing Gall’s stepwise development.

Key Insight

Functional complexity must be grown, not designed whole.Gall’s Law isn't really about minimalism. It's about iterative evolution, where every step has to produce something that works as a coherent whole.

References

  • Gall, J. (1975). Systemantics: How Systems Really Work and Especially How They Fail. Quadrangle/New York Times Book Co.
  • Darwin, C. (1859). On the Origin of Species. London: John Murray.
  • Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley.
  • Conway, M. E. (1968). “How Do Committees Invent?” Datamation, 14(4), 28–31.
  • Ashby, W. R. (1956). An Introduction to Cybernetics. Chapman & Hall.

More Resources