Alexander has the concept of unselfconscious design under circumstances where change transcend the obvious thing to do, for example the innate ability of engineers to tinker and get things going. to what extent do the authors support this thinking and to what extent are the ideas counter intuitive
The sources provide significant support for the concept of unselfconscious design—often discussed as tinkering, bricolage, or muddling through—viewing it as a vital strategy for navigating complex systems where linear planning fails. However, they also highlight that this approach is highly counter-intuitive to modern management orthodoxies that demand “fail-safe” predictions and expert control.
Authors Supporting Unselfconscious “Tinkering”
Many authors in the sources argue that in complex domains, the innate ability to experiment and adjust is more effective than top-down engineering:
• Nassim Taleb and “Antifragility”: Taleb is a staunch supporter of “stochastic tinkering” and bricolage[1]. He argues that practical “know-how” (the green lumber trader) often supersedes theoretical “know-what” (the academic), and that systems should be allowed to experience small, local failures—mistakes—to gain information and remain resilient[2].
• Herbert Simon and “Recognition”: Simon demystifies the “innate ability” of experts by defining intuition as recognition[5]. He posits that experienced engineers recognize familiar patterns (“chunks”) stored in memory, allowing them to access solutions rapidly and unselfconsciously without the need for exhaustive analytical search[5].
• John Flach and “Muddling Through”: Flach advocates for a strategy of incrementalism or “muddling through”[6][7]. In “wicked” systems, he argues the most rational path is not perfect foresight, but making small, reversible moves and correcting course based on feedback from the environment[6][8].
• Humberto Maturana and “Natural Drift”: Maturana views system change not as engineering toward a goal, but as natural drift[9]. Systems and their environments “structurally couple” through recurrent interactions, meaning the system changes its structure spontaneously to maintain its identity without a conscious plan[10][11].
• Stafford Beer and “Riding the Dynamics”: Beer suggests that instead of trying to specify every rule in advance, managers should “ride the dynamics of the system,” allowing solutions to arrive via dynamic processes rather than a central controller[12][13].
Why These Ideas are Counter-Intuitive
The sources suggest that unselfconscious design is counter-intuitive because it contradicts the “Old Enlightenment” view of reason:
• The Illusion of Control: Modern management often functions as an “omniscient conqueror,” assuming that with enough data, outcomes can be predicted and controlled[14]. The idea that an engineer can “tinkeringly” nudge a system without a master plan is seen as unprofessional or “unscientific” by those in the “Complicated” domain[3][15].
• Direct vs. Systemic Causation: George Lakoff notes that the human brain is wired for “Direct Causation” (A causes B), which is encoded in our very grammar[16][17]. Unselfconscious design relies on “Systemic Causation,” which involves indirect and probabilistic effects that are harder for the conscious mind to track[17].
• The “Error of the Third Kind”: Ian Mitroff warns that unreflective tinkering can lead to E3 (solving the wrong problem precisely)[18]. Without shifting one’s mindset to see the “mess” or the “whole system,” localized tinkering might inadvertently improve a part while damaging the whole[18][19].
• Cognitive Burden: John Warfield argues that “unaided” human intuition is limited by Miller’s Limit (the mind can only hold about seven items)[20][21]. He views “unconscious” design as prone to Spreadthink and behavioral pathologies, advocating instead for highly structured, disciplined collective inquiry[20][22].
Summary Table: Tinkering vs. Engineering
| Feature | Unselfconscious “Tinkering” | Self-Conscious “Engineering” |
|---|---|---|
| Logic | Abduction (best guess/hunch)[23] | Deduction/Induction[24] |
| Pace | Incremental/Iterative[7] | Linear/Sequential[25] |
| Goal | Satisficing (good enough)[26] | Optimization (the best)[27] |
| Source | Experiential “Deep Smarts”[28] | Programmed Knowledge (P)[29] |
| View of Future | Indeterminate/Unknowable[30] | Predictable/Plannable[31] |
In your current situation, is the “tinkering” of your engineers being treated as a valuable adaptive signal, or is it being suppressed by a management structure that demands a “fail-safe” master plan?
References
[1] 💬Nutshell (Process).md [2] 💬Gists.md [3] 💬Questions.md [5] 💬Gists.md [6] 💬Gists.md [7] 💬Nutshell (Process).md [8] 💬What is Complexity.md [9] 💬Questions.md [10] 💬Gists.md [11] 💬Nutshell (Process).md [12] 💬What is Complexity.md [13] 💬What is Complexity.md [14] 💬What is Complexity.md [15] 💬What is Complexity.md [16] 💬Gists.md [17] 💬Questions.md [18] 💬Questions.md [19] 💬Nutshell (Process).md [20] 💬Gists.md [21] 💬Gists.md [22] 💬Gists.md [23] 💬Keywords + Jargon.md [24] 💬Questions.md [25] 💬Distinctions.md [26] 💬Gists.md [27] 💬Distinctions.md [28] 💬Gists.md [29] 💬Gists.md [30] 💬Keywords + Jargon.md [31] 💬Distinctions.md