To “climb the tower” using Ashby’s Law of Requisite Variety is to move from the Engineering level of building response mechanisms to the Systems Thinking level of managing the architecture of variety itself[1][2]. This process shifts your focus from the technical “How” of control to the contextual “Why” of relationship maintenance[1][3].
Here is how the climb unfolds using Ashby’s Law as your guide:
Level 4: Engineering (The “How”)
At the base of the tower, you are focused on Variety Engineering[4]. The primary task is to balance the variety equation by building attenuators (to filter incoming environmental noise) and amplifiers (to boost your own response capacity)[5][6]. In an organizational setting, this looks like creating standard operating procedures or hiring more staff to handle a surge in customer demands[7].
Level 3: Science (The “What”)
As you climb to the Science level, you shift from building tools to measuring and modeling the system’s behavior[8]. You treat the situation as a “Black Box,” observing the inputs and outputs to deduce its internal variety (the number of possible states it can occupy)[9][10]. At this stage, you are applying the Conant-Ashby Theorem, which proves that any successful regulator must be a functional model of the system it is trying to regulate[11][12].
Level 2: Systems Thinking (The “Why”)
The climb is complete when you reach the Systems Thinking level, where you investigate the context and relationships[1][13]. Instead of asking how to control the system, you ask “Why is the system producing this specific variety rather than something else?”[14][15].
• Negative Explanation: You look for the constraints—the “mould” of rules and laws that limit the system’s behavior—rather than looking for a direct cause[15][16].
• Shifting Boundaries: You realize that the “system” is an observer-dependent choice[17]. You may find that by expanding the boundary of what you consider the “system,” you can move a previously uncontrollable environmental factor into your span of control[18][19].
The Result of the Climb
By climbing the tower with Ashby’s Law, you move from Optimization (doing the current thing perfectly) to Viability (ensuring the system can adapt to anything the environment throws at it)[20][21]. You stop trying to “solve” the problem and instead start “dancing” with the system, managing the starting conditions so that desirable patterns emerge spontaneously[22][23].
--------------------------------------------------------------------------------
In your current work, are you finding yourself stuck at the Engineering level, trying to build more “amplifiers” to handle the workload, or are you ready to climb to the Systems level to question why that variety is being generated in the first place?
References
[1] 💬Questions.md [2] 💬What is Complexity.md [3] 💬Questions.md [4] 💬Nutshell (Process).md [5] 💬Environment.md [6] 💬Nutshell (Process).md [7] 💬What is Complexity.md [8] 💬Questions.md [9] 💬How To Guides.md [10] 💬How To Guides.md [11] 💬Environment.md [12] 💬Keywords + Jargon.md [13] 💬Questions.md [14] 💬Questions.md [15] 💬Questions.md [16] 💬Questions.md [17] 💬Perspectives.md [18] 💬Environment.md [19] 💬Environment.md [20] 💬Distinctions.md [21] 💬Keywords + Jargon.md [22] 💬Questions.md [23] 💬What is Complexity.md