Look, if you want the truth about the state of Systems Thinking today, you have to accept that we are living through a “success catastrophe”[1]. The discipline has become a “bushfire”—a runaway blaze of isolated techniques and consultant-friendly jargon that has burned away the coherent center of the subject[2],[3].
We are drowning in “splendid nonsense”[4],[5]. If you want to actually understand this mess, you have to stop chasing the latest LinkedIn gurus and go back to the “Old Books”—the foundational work of Ashby, Weaver, and Vickers[6],[7].
Here is what you actually need to know, stripped of the mysticism.
1. The “Goldilocks Zone” of Middle NumbersForget the “edge of chaos” rhetoric. The real definition of complexity was laid out by Warren Weaver in 1948, and we’ve largely ignored it. Science handles “Organized Simplicity” (machines) and “Disorganized Complexity” (gas molecules) very well[8],[9]. The problem—and the only place Systems Thinking actually applies—is the “Middle Numbers”[10],[11].This is the Goldilocks Zone of Organized Complexity: systems with too many parts to calculate individually but too few to average out statistically[12],[13]. If you aren’t operating here, you aren’t doing systems thinking; you’re just doing bad physics or bad statistics[14].
**2. The Epistemic Cut (Stop Confusing the Map with the Territory)**Most people in this field are suffering from the “Fallacy of Misplaced Concreteness”[15],[16]. You must understand the “Epistemic Cut”—the hard distinction between the material world and the abstract world[17],[18].
• Laws are ontological: they are universal, physical, and you cannot break them (e.g., gravity, thermodynamics)[19],[20].
• Rules are epistemological: they are local, arbitrary, and structure-dependent (e.g., traffic laws, genetic codes)[21],[20].”Systems” do not exist in the real world; they are mental constructs we use to organize our ignorance[22],[23]. As Checkland rightly noted, the “system” is the process of inquiry, not the thing being studied[24],[25]. If you think the system is a physical object, you are engaging in “reification” and you will eventually hit a wall[26],[27].
**3. The “Stone Bridge” (Structure Dominates Material)**Emergence isn’t magic; it’s architecture. Look at a stone bridge. The stones want to fall down (gravity/Laws). The bridge stands up (Emergence/Rules). Why? Because the structure allows the whole to transcend the properties of the parts[28],[29].This is the “Stone Bridge” principle: architecture (relationships) dominates material[30],[31]. But remember: the bridge is “meta-stable.” It relies on a “frozen history” of construction—scaffolding that was once there and is now gone[32],[33]. If you ignore the history and the physical constraints, your model is just a hallucination[34],[29].
4. The “Tosh” of Information EntropyWe need to be very careful with the concept of Entropy. Unless you are grounded in the physical realities of P.W. Atkins and thermodynamics, you are likely talking “tosh”[35],[36].There is a massive confusion between Shannon Information (a probabilistic measure of signal uncertainty) and Thermodynamic Entropy (energy dispersal)[37],[38]. Management consultants love to mix these up to sound profound, but without a physical mechanism, “information” causes nothing[39],[40]. Information is a description of the world, not a force within it[41],[42].
5. Negative Explanation (How to Actually Think)If you want to solve a problem, stop asking “What caused this?” That’s linear thinking. You need to adopt Negative Explanation[43].As Geoffrey Vickers taught us, the real question is: “Why is the system doing this, rather than something else**?”**[44],[45].You must look for the constraints—the things preventing the system from doing all the other possible things[46],[47]. This is Ashby’s Cybernetics: observing “what might have happened, but did not”[48],[49].
ConclusionWe need to stop “playing concept bingo” with new terms for old ideas[50]. Systems Thinking is a craft skill of navigating between the real world (the mess) and the abstract world (the model) without forgetting which is which[51],[52]. It is about “muddling through” and finding “clumsy solutions” because, in the end, all models are wrong—the only question is how wrong they have to be to not be useful[4],[53].
References
[1] Recent.pdf [2] Perlite.pdf [3] Recent.pdf [4] Perlite.pdf [5] Perlite.pdf [6] Perlite.pdf [7] Recent.pdf [8] Perlite.pdf [9] Recent.pdf [10] Perlite.pdf [11] Perlite.pdf [12] Perlite.pdf [13] Recent.pdf [14] Perlite.pdf [15] Perlite.pdf [16] Perlite.pdf [17] Perlite.pdf [18] Recent.pdf [19] Perlite.pdf [20] Recent.pdf [21] Perlite.pdf [22] Perlite.pdf [23] Perlite.pdf [24] Perlite.pdf [25] Recent.pdf [26] Perlite.pdf [27] Recent.pdf [28] Perlite.pdf [29] Recent.pdf [30] Perlite.pdf [31] Perlite.pdf [32] Perlite.pdf [33] Perlite.pdf [34] Perlite.pdf [35] Perlite.pdf [36] Recent.pdf [37] Perlite.pdf [38] Recent.pdf [39] Recent.pdf [40] Recent.pdf [41] Recent.pdf [42] Recent.pdf [43] Recent.pdf [44] Recent.pdf [45] Recent.pdf [46] Perlite.pdf [47] Recent.pdf [48] Perlite.pdf [49] Recent.pdf [50] Recent.pdf [51] Perlite.pdf [52] Perlite.pdf [53] Perlite.pdf