John C. Gall Jr. (1925–2014) was a pediatrician and author. In Systemantics, later expanded as The Systems Bible, he used satire and case histories to explore why human-made systems can behave unexpectedly and depart from their intended functions. — John Gall Obituary.

Infographic for "Lessons from John Gall".

Fundamental Principles and The Nature of Systems

  1. Start With a Working Simple System: Gall argues that a working complex system usually grows out of a simpler one that already worked; designing the complex version from scratch is a poor starting point. — The Systems Bible.
  2. See the Universe as a Large System: Gall contrasts the familiar machine metaphor with the universe behaving, in his framing, more like a very large system. — The Systems Bible.
  3. Expect Systems to Misbehave: Gall treats failure to function as expected as a recurring feature of systems behavior, not just an isolated defect in one organization. — The Systems Bible.
  4. Beware the Seduction of Systems: A system may promise to simplify work yet consume time and effort in its own upkeep and create new problems. — The Systems Bible.
  5. New Systems Bring New Problems: Gall’s fundamental theorem is that setting up a system creates a new entity with its own operational problems. — The Systems Bible.
  6. Systems Persist and Grow: Gall likens systems to babies: once established, they tend to persist, grow, and encroach. — The Systems Bible.
  7. Growth Brings Encroachment: Gall says expanding systems can intrude on adjacent activities and increasingly shift work onto people meant to benefit from them. — The Systems Bible.
  8. Expect Unexpected Behavior: Gall’s Generalized Uncertainty Principle says complex systems exhibit behavior that their designers did not anticipate. — The Systems Bible.
  9. Learn How to Cope With Systems: Gall’s own response to system failures is to learn the recurring patterns of systems behavior; he credits the separate coping aphorism to Virginia Satir. — The Systems Bible.

How Systems Behave and Misbehave

  1. Systems Can Oppose Their Functions: Gall argues that a system can obstruct the very function for which it was established. — The Systems Bible.
  2. Roles Can Diverge From Actual Work: Gall distinguishes what people in a system are said to do from what their work actually produces. — The Systems Bible.
  3. The System May Not Do What It Claims: Gall’s operational fallacy warns that a system’s declared function can differ from what its operations actually accomplish. — The Systems Bible.
  4. Names Do Not Make Functions Identical: Gall says the same-named function can be operationally different when performed by a person, a small system, or a larger system. — The Systems Bible.
  5. Large Systems Resist Complete Evaluation: Gall presents the difficulty of evaluating large systems and notes that even the criteria for success or failure may be disputed. — The Systems Bible.
  6. A System Has Many Ways to Fail: Gall’s failure theorem emphasizes that there may be indefinitely many ways for a system to malfunction. — The Systems Bible.
  7. Structure May Not Predict Failure Mode: Gall argues that the particular way a complex system fails cannot usually be inferred from its design alone. — The Systems Bible.
  8. Fail-Safe Design Can Fail: Gall’s fail-safe theorem warns that a supposedly protective mechanism can itself be the point of failure. — The Systems Bible.
  9. Triumph Can Precede Malfunction: Gall notes a tendency for systems to malfunction conspicuously after a celebrated success, when old strategies are applied to new conditions. — The Systems Bible.
  10. Treat the Five-Percent Claim as Satire: Gall offers low efficiency as a satirical axiom about complicated systems, not a measured universal rate. — The Systems Bible.
  11. Malfunction May Remain Hidden: Gall’s functional-indeterminacy theorem says serious malfunction can go undetected for a long time in complex systems. — The Systems Bible.
  12. Define Success Before Judging a System: Gall argues that evaluating a large system depends on what it is supposed to do and which consequences count as success or failure. — The Systems Bible.

The Goals and Purpose of Systems

  1. Systems Develop Internal Goals: Gall describes systems as developing goals of their own that can diverge from the goals of their designers. — The Systems Bible.
  2. Check the Function Behind the Name: Gall warns that a system’s named function can resemble its actual operation less and less as the system grows. — The Systems Bible.
  3. Anticipate Exploitation: Gall’s exploitation theorems warn that systems can attract people who find ways to use them for unintended ends. — The Systems Bible.
  4. Distinguish Purpose From Stated Goal: Gall sets aside an unknowable ultimate purpose and asks what the system can actually be used for. — The Systems Bible.
  5. Expect Institutional Inertia: Gall says systems tend to keep operating in familiar ways even after conditions or the original need change. — The Systems Bible.
  6. Great Advances May Come From Elsewhere: Gall argues that systems established to produce great advances are not necessarily where major advances originate. — The Systems Bible.

On Information and Perception within Systems

  1. Needed Information May Be Unavailable: Gall’s inaccessibility theorem separates the information available, desired, needed, and obtainable. — The Systems Bible.
  2. Systems Filter Reality: Gall argues that insiders encounter a version of the outside world filtered through a system’s limited channels of perception. — The Systems Bible.
  3. Reports Can Become Official Reality: Gall’s administrative law says systems tend to treat reported facts as the facts that count. — The Systems Bible.
  4. Beware Wishful Feedback: Gall warns that a system can misread its inputs and build an increasingly unrealistic model of the world while seeming to receive feedback. — The Systems Bible.
  5. Question Claims of Inevitability: Gall names the assumption that things must remain as they are the inevitability-of-reality fallacy. — The Systems Bible.
  6. Large Systems Narrow the Interface: Gall says a growing system can reduce its dealings with an individual to a narrow, specialized representation. — The Systems Bible.
  7. Feedback Must Change the Course: For Gall, information becomes effective feedback only if the system changes direction in response. — The Systems Bible.

Anergy and Problem Solving

  1. Define the Anergy-State: Gall uses anergy for a condition that takes human effort or ingenuity to bring closer to human desires or needs. — The Systems Bible.
  2. Conservation of Anergy: Gall presents the amount of anergy as constant within his satirical system of axioms; this is his framing, not an empirical physical law. — The Systems Bible.
  3. Systems Redistribute Anergy: In Gall’s framework, a system reshapes and redistributes problems rather than making them disappear. — The Systems Bible.
  4. A System Is a Proposed Solution: Gall distinguishes a system built as someone’s answer to a problem from actual resolution of that problem. — The Systems Bible.
  5. Avoid Creating a Second Problem: Gall warns that building a system to solve a problem can leave both the original problem and the new system to manage. — The Systems Bible.

Practical Advice and Learnings

  1. Avoid an Unnecessary New System: Gall’s design advice begins by asking whether the work can be done without creating a new system. — The Systems Bible.
  2. Tread Softly Around Existing Systems: Gall cautions that a new system can disturb an older one that is already functioning. — The Systems Bible.
  3. Leave Room for Looseness: Gall argues that loosely coupled systems can last and function better than tightly constrained ones. — The Systems Bible.
  4. Design With Human Tendencies: Gall’s downhill-design metaphor urges designers to work with human tendencies rather than against them. — The Systems Bible.
  5. Remember the Cost of Getting Out: Gall includes Agnes Allen’s law to warn that dismantling a system can be harder than establishing it; the aphorism is credited to Allen. — The Systems Bible.
  6. Recognize the Systems-Person Perspective: Gall says immersion in a system can isolate people from alternative experiences and distort their view of what is happening outside it. — The Systems Bible.
  7. Systems Attract Systems-People: Gall argues that systems attract people adapted to succeeding within them, though those traits may not serve the system’s stated purpose. — The Systems Bible.
  8. Specialization Can Become Bizarre: Gall argues that prolonged selection for a narrow system can produce increasingly unusual specializations. — The Systems Bible.
  9. Perfect Planning Can Signal Decay: Gall lists perfection of planning among signs that a system is applying old success patterns to new circumstances. — The Systems Bible.
  10. Examine How the Outcome Was Produced: Gall contrasts fixation on end results with analysis of how systems work and why an outcome occurred. — The Systems Bible.
  11. Accept Partial, Temporary Success: Gall describes error as part of the human situation and successes as temporary and partial, using humor to make that lesson bearable. — The Systems Bible.
  12. Treat Solutions as Continuing Responses: Gall argues that a solution is a response within an ongoing interaction: the problem can change in turn and require another response. — The Systems Bible.
  13. Observation Can Change the System: Gall argues that probing a system can alter both the system and the observer’s understanding of it. — The Systems Bible.
  14. Study Systems, Not Just Their Errors: Gall argues that understanding systems in general matters more than criticizing one particular system’s mistakes. — The Systems Bible.
  15. Temporary Patches Can Persist: Gall warns that a temporary patch may become a permanent feature of a system. — The Systems Bible.
  16. Data Gathering Can Delay Action: Gall says prolonged information-gathering can become a way to avoid addressing a difficult problem. — The Systems Bible.
  17. Avoid Preparing Only for the Past: Gall warns that a strategy that succeeded before can leave a system ready for yesterday’s challenge rather than today’s. — The Systems Bible.

Learn more:

  1. The Systems Bible: The Beginner’s Guide to Systems Large and Small — Full Text: Gall’s original 2002 third edition, including the annotated compendium. — The Systems Bible — Full Text.
  2. John C. Gall Jr. — Family Obituary: Family-authored biographical account and publication history. — John Gall Obituary.