Yes, the diverse advice from these authors can be integrated into a unified Framework for Action. While the authors disagree on the nature of reality (ontology), they largely agree on a diagnostic process: how you act depends on what kind of system you are facing.
The framework below synthesizes the advice into four phases: Cognitive Stance, Diagnosis, Intervention Strategy, and Feedback.
The Integrated Action Framework
Phase 1: Establish the Cognitive Stance (Epistemology)
Before acting, you must adjust your own mindset.
• Abandon “God-like” Objectivity: Accept that you are inside the system, not outside looking in (Rittel[1],[2]).
• Be Modest: Acknowledge that your model is not reality. It is a limited, provisional filter (Cilliers[3], Checkland[4]).
• Value “Stuckness”: If you are confused, do not panic. Treat “stuckness” as the necessary precursor to new insight (Dynamic Quality) rather than a failure of intellect (Pirsig[5],[6]).
Phase 2: Diagnose the Domain (Ontology)
Determine the nature of the beast. Is it a “clock” (ordered) or a “cloud” (complex)?
• The Rosen Test: Is the system simulable? If you can write an algorithm that captures it fully, it is “Simple.” If it has no largest model, it is “Complex” (Rosen[7]).
• The Snowden Test: Is causality repeating? If yes, you are in the Ordered domain. If causality is only coherent in retrospect, you are in the Complex domain (Snowden[8]).
• The Rittel Test: Is there a stopping rule? If the problem has a clear solution, it is Tame. If every attempt to solve it changes the problem, it is Wicked (Rittel[9],[10]).
Phase 3: Select the Strategy
Based on Phase 2, choose one of three paths:
• Path A: The Engineer (for Ordered/Simulable Systems)
◦ Goal: Optimization and Efficiency. ◦ Action: Find the Constraint (Archimedes point) and manage it (Dettmer[11]). ◦ Method: Use Hierarchy to decompose the system into stable subsystems (Simon[12]). ◦ Result: Design a “fail-safe” solution (Hock[13]). • Path B: The Navigator (for Complex/Natural Systems)
◦ Goal: Adaptation and Viability. ◦ Action:Probe-Sense-Respond. Launch safe-to-fail experiments to see what patterns emerge (Snowden[14], Shannon[15]). ◦ Method:Match Variety. Ensure your ability to respond is as complex as the system’s ability to change (Beer[16]). ◦ Filter: Do not model the whole; use Minimalist Intervention to filter the flux (Wilk[17]). • Path C: The Facilitator (for Social/Messy Systems)
◦ Goal: Learning and Accommodation. ◦ Action:Sweep in the Environment. Include ethical and political considerations, even “enemies” (Churchman[18]). ◦ Method: Use systems models as Debating Tools to align conflicting worldviews (Checkland[19]). ◦ Result:Dissolve the problem by redesigning the context (Ackoff[20]).
The Framework Diagram
Here is the integrated advice visualized as a Mermaid flow chart.
graph TD Phase 1: Cognitive Stance subgraph Cognitive_Stance [Phase 1: Cognitive Stance] Think_2ndOrder["Accept you are<br/>INSIDE the system<br/>(Rittel/TOG)"] Modesty["Adopt Modesty:<br/>Models are not Reality<br/>(Cilliers/Checkland)"] Value_Stuckness["Value 'Stuckness'<br/>as Precursor to Insight<br/>(Pirsig)"] end Phase 3: Strategy subgraph Strategy [Phase 3: Strategy Selection] Path B: Complex Path_B[/"PATH B: The Navigator<br/>(Complex/Natural)"/] Probe["Probe-Sense-Respond<br/>(Snowden)"] Variety["Match Variety<br/>(Beer)"] Filter["Filter the Flux<br/>(Wilk)"] Phase 4: Feedback subgraph Feedback_Loop [Phase 4: Adaptation] Emergence["Observe Emergence<br/>(Juarrero/McMaster)"] Learning["Update Mental Models<br/>(Senge/Checkland)"] end Path A Flow Path_A --> Constraint Constraint --> Decompose Decompose --> Design Design --> Emergence Path C Flow Path_C --> Sweep Sweep --> Debate Debate --> Dissolve Dissolve --> Emergence Styling style Start fill:#f9f,stroke:#333,stroke-width:2px style Path_A fill:#d1e7dd,stroke:#333 style Path_B fill:#fff3cd,stroke:#333 style Path_C fill:#f8d7da,stroke:#333 style Cognitive_Stance fill:#e2e3e5,stroke:#333,stroke-dasharray: 5 5
Key Integration Points in the Diagram
1. The “Rosen Test” Branching: The diagram uses Robert Rosen’s strict definition of simulability[7] as the primary fork. If a system is simulable (a “trivial machine” in Rittel’s terms[21]), you use Path A (Engineering). This satisfies the “Systems Thinking” group (Dettmer, Simon).
2. The “Social” vs. “Natural” Split: If the system is complex, the diagram splits again based on the “nature” of the complexity.
◦ If it involves physical/biological adaptation (Natural), it follows Path B (Snowden/Beer), focusing on probing and variety matching[14],[16]. ◦ If it involves human meaning and conflicting values (Social), it follows Path C (Checkland/Ackoff), focusing on debate and problem dissolution[19],[20]. 3. The “Filter” Mechanism: James Wilk’s advice to “filter the flux”[17] is placed in Path B. Since you cannot model the whole complex system (Cilliers[3]), you must intervene minimally to create constraints that filter the outcome, rather than trying to control the cause.
4. The Feedback Loop: The process returns to the start because, as Rittel argues, there is “no stopping rule” for wicked problems[10]; the “solution” to one problem generates the next generation of problems (Ackoff’s “Mess”[22]).
References
[1] Horst Ritell.md [2] Horst Ritell.md [3] Paul Cilliers.md [4] Peter Checkland.md [5] Robert Pirsig.md [6] Robert Pirsig.md [7] Relational Biologists - Robert Rosen Howard Pattee Dennis Noble.md [8] Dave Snowden.md [9] Horst Ritell.md [10] Horst Ritell.md [11] Theory of Constraints.md [12] Herb Simon.md [13] Dee Hock.md [14] Dave Snowden.md [15] Claude Shannon.md [16] Stafford Beer.md [17] James Wilk.md [18] C. West Churchman.md [19] Peter Checkland.md [20] Russ Ackoff.md [21] Horst Ritell.md [22] Russ Ackoff.md