In an article last February on software development culture, eWeek’s Peter Coffee made reference to a maxim on complexity: “Complex systems usually operate in failure mode.” The source was John Gall’s 1978 work called Systemantics, a kind of satire of General Systems Theory that simultaneously mocked and catalogued the tendencies of systems to create their own problems. With its title taken from a mash-up of systematic, semantic, and ’system antic,’ the book laid out a quite illuminating series of ‘laws’ that afflict systems in the same fashion that the Peter Principle underlies corporate hierarchy, Conway’s Law outlines the effect of committees, and Murphy’s Law describes probability—in fact, one law is that “a complex system can fail in an infinite number of ways” which essentially encapsulates Murphy. Gall also ventures into policy, arguing for a much broader understanding of global concerns as being generated by underlying systems:

“The religious person may blame it on original sin. The historian may cite the force of trends such as population growth and industrialization. The sociologist offers reasons rooted in the peculiarities of human associations. Reformers blame it all on ‘the system,’ and propose new systems that would, they assert, guarantee a brave new world of justice, peace, and abundance. Everyone, it seems, has his own idea of what the problem is and how it can be corrected. But all agree on one point—that their own system would work very well if only it were universally adopted.

The point of view espoused in this essay is more radical and at the same time more pessimistic. Stated as succinctly as possible: the fundamental problem does not lie in any particular system but rather in systems as such. Salvation, if it is attainable at all, even partially, is to be sought in a deeper understanding of the ways of systems, not simply in a criticism of the errors of a particular system.”

Other references to Systemantics include excerpts of the 3rd edition (renamed The System Bible) via Amazon’s Online Reader—for example, you can browse the entire “Index of Horrible Examples” from Czar Alexander to Three Mile Island and the Titanic—and collected references via del.icio.us. Regrettably Amazon does not actually sell any of the 3 editions, but another company called General Systemantics advertises copies for sale (via a default MS FrontPage theme, itself fodder for a whole article on system failure) along with the brilliantly epigrammatic praise by William Safire that “Work books gall, but Gall’s book works.”

More contemporary parallels to Gall’s work include Donella Meadows’ Twelve Leverage Points which describe a scale of effective places “to intervene in a system,” alternately thought of as levers by which you can affect the workings of a complex system; Edward Tenner’s book Why Things Bite Back on the ‘revenge effects’ or unintended consequences of technology; Jared Diamond’s book Collapse on possible causes of failed societies; and Anti-patterns, an outgrowth of Design Patterns that have been utilized in fields like architecture and software design to find well-solved problems and re-use them. Most anyone who’s held a job can probably relate to one or more organization or management anti-patterns, which also includes longstanding concepts such as “moral hazard” from economics and “scope creep” from project management.

[EB: Systems Engineering]