Can you be specific about the position taken by snowden and hoverstadt with respect to unselfconscious design
Both Dave Snowden and Patrick Hoverstadt provide strong support for the logic of unselfconscious design—the idea that in complex environments, “tinkering” and emergent adaptation are more effective than top-down engineering[1]. However, they approach this from different systemic angles: Snowden focuses on the epistemic process of probing, while Hoverstadt focuses on the structural requirement for autonomy.
Dave Snowden: Designing for Emergence
Snowden’s position is rooted in the Complex domain of his Cynefin framework, where cause and effect are only visible in retrospect[4].
• Safe-to-Fail Probes: Snowden explicitly rejects “fail-safe” design in complex contexts[1][7]. Instead, he advocates for safe-to-fail experimentation, which is essentially a structured form of tinkering[1][3].
• Emergent Practice: He argues that in complex systems, “best practice” is a category error because what worked yesterday may not work today[8]. Instead, the designer must “probe, sense, and respond,” allowing a solution to emerge from the system’s reaction to small interventions[9][10].
• Human Sensor Networks: Snowden handles the “unselfconscious” element by utilizing distributed cognition[11]. By using large groups of people to detect “weak signals,” he allows the organization to “sense” a solution before it is consciously formulated by an expert[12][13].
Patrick Hoverstadt: Variety Engineering and Autonomy
Hoverstadt’s position is built on Managerial Cybernetics (Stafford Beer’s Viable System Model) and the “Grammar” of Systems Laws[2].
• POSIWID (Purpose Is What It Does): Hoverstadt adheres to the principle that a system’s true purpose is revealed by its actual behavior and outputs, not its stated design or mission statement[16]. This validates unselfconscious design because it prioritizes the reality of what the system is “tinkeringly” achieving over what was planned[18][19].
• The Autonomy Dilemma: Hoverstadt argues that to handle high environmental complexity, a system must grant maximum autonomy to its operational units (System 1)[20][21]. This structurally mandates unselfconscious design: the “engineers at the coalface” must be free to tinker and adapt to local variety without waiting for a self-conscious master plan from the center[21][22].
• Structural Coupling: He views the relationship between an organization and its environment as structural coupling, where the system and environment “drift” together through recurrent interactions[23][24]. This is an unselfconscious evolutionary process where the system’s structure changes spontaneously to maintain a “fit” with its context[25][26].
Summary Table: Unselfconscious Stances
| Feature | Dave Snowden | Patrick Hoverstadt |
|---|---|---|
| View of Tinkering | Safe-to-Fail Probes: Small, parallel experiments to reveal patterns[1][7]. | Variety Engineering: Local units must have autonomy to match environmental variety[21][22]. |
| Source of Order | Emergence: Order arises from the interaction of agents, not a blueprint[1][27]. | Systems Laws: Order is maintained by universal cybernetic laws (e.g., feedback loops)[14][28]. |
| Designer’s Role | Managing “starting conditions” and vectors of change[1][29]. | Designing a viable structure that enables self-regulation[20][30]. |
| Evaluation | Detecting “weak signals” and outliers in the human network[31][32]. | POSIWID: Judging the system by what it actually produces in the environment[16][18]. |
--------------------------------------------------------------------------------
In your current situation, are you more inclined to adopt Snowden’s “probe-first” mindset to see what patterns emerge, or do you see the need for Hoverstadt’s structural shift to grant your “tinkerers” the formal autonomy they need to be effective?
References
[1] 💬Distinctions.md [2] 💬Gists.md [3] 💬What is Complexity.md [4] 💬Distinctions.md [7] 💬Nutshell (Process).md [8] 💬What is Complexity.md [9] 💬Gists.md [10] 💬Nutshell (Process).md [11] 💬Nutshell (Process).md [12] 💬Perspectives.md [13] 💬Perspectives.md [14] 💬Gists.md [16] 💬Environment.md [18] 💬Keywords + Jargon.md [19] 💬Questions.md [20] 💬Keywords + Jargon.md [21] 💬Nutshell (Process).md [22] 💬Nutshell (Process).md [23] 💬Keywords + Jargon.md [24] 💬Nutshell (Process).md [25] 💬Environment.md [26] 💬Nutshell (Process).md [27] 💬Distinctions.md [28] 💬Questions.md [29] 💬Questions.md [30] 💬What is Complexity.md [31] 💬Perspectives.md [32] 💬Perspectives.md