Design Evolution: Simplicity Breeds Endurance
What Is Good Design?
Today’s Lens: John Gall — Evolve from a Simple System That Works
“A complex system that works is invariably found to have evolved from a simple system that worked.” — John Gall, Systemantics
Gall’s deep take: good design resists the fantasy of “comprehensive” solutions. Systems that endure don’t spring forth fully formed; they accrete. You start with a working nucleus, then evolve—preserving reliability while increasing scope. The trap is launching complexity before you’ve earned it; premature intricacy multiplies failure modes faster than learning can keep up.
A short expansion
- Treat every added capability as a bet against stability. The designer’s craft is sequencing: protect a small, dependable core; expand via reversible steps; harvest feedback to decide what deserves permanence. Complexity should be the residue of validated usefulness, not ambition.
Try it (5 minutes)
- Define your “working kernel”: the smallest flow that must never break (write its success/failure signals).
- Add one extension behind a “kill switch” and a clear rollback plan; ship only what you can safely undo.
- Track “stability margin”: for every new feature, log one new test, one monitor, and one documented exit path.
Sources
- Gall, J. (1975). Systemantics: How Systems Really Work and How They Fail. See overview of Gall’s Law and background on Systemantics/The Systems Bible.
- Gall, J. (2012). The Systems Bible: The Beginner’s Guide to Systems Large and Small (updated edition). Publisher’s page (context and summaries).