Based on the sources—explicitly excluding the Cynefin framework—I have developed The “Systemic Triage” Framework.
This framework replaces the Cynefin categorizations with distinctions drawn from Relational Biology (Rosen), Social Systems Theory (Jackson/Flood), and Hierarchy Theory (Allen/Simon). It guides you through three specific “Decision Points” to select the appropriate methodology.
--------------------------------------------------------------------------------
Phase 1: The Pre-Diagnosis (Clearing the View)
Before selecting a route, you must strip away abstract confusion.
• The “Video Description” Rule: Do not start with abstract labels (e.g., “morale is low”). Climb down the ladder of abstraction to “video descriptions”—concrete facts that a camera could record[1].
• Empty the Tea Cup: Adopt a “beginner’s mind.” Use a slip system to offload ideas so you can perceive the situation without the interference of old thoughts[2][3].
• Essential Selection: Master the art of ignoring variables. Use “orientation” to decide what to discard before you attempt to analyze[4][5].
--------------------------------------------------------------------------------
Phase 2: The Decision Matrix
Decision Point A: The Rosen Test (Simulability)
Question: Can the system be fully described by a formal set of rules or a simulation, and can it be decomposed into parts without losing its function?
• YES (It is a Mechanism): It is a “Trivial” or “Simple” system (in the Rosennean sense). It is weak in entailment and causally linear[6].
◦ → Go to Route 1: The Engineer (Optimization) • NO (It is a Complex/Living System): It possesses internal causal loops, non-computable models, or social agency[6][7].
◦ → Proceed to Decision Point B.
Decision Point B: The Jackson Test (Goal Alignment)
Question: Do the stakeholders involved agree on the goal/purpose of the system?
• YES (Unitary): The goal is agreed upon (e.g., “Survival,” “Profit,” “Health”), but the path is unclear or the environment is turbulent.
◦ → Go to Route 2: The Ecologist (Adaptation) • NO (Pluralist/Coercive): There are conflicting values, worldviews, or power imbalances. The “problem” is actually a disagreement on what constitutes a solution.
◦ → Go to Route 3: The Diplomat (Negotiation)
Decision Point C: The Stability Test (The Muddle)
Question: Is the system currently stable enough to model, or is it in a state of “Runaway” or overwhelming confusion?
• RUNAWAY/MUDDLE: High entropy, rapid collapse, or “transcomputational” possibilities[8].
◦ → Go to Route 4: The Stabilizer (Crisis Management) --------------------------------------------------------------------------------
Route 1: The Engineer (Optimization)
Context: Manufacturing, Logistics, Software Code, Mechanical Systems.Goal: Efficiency, Resolution, and the “Ideal Final Result.”
• Methodology 1: Theory of Constraints (Dettmer): Treat the system as a chain. Use Logic Trees to identify the single “weakest link” (Constraint). Focus all resources on the “Archimedes Point” to maximize throughput[9][10].
• Methodology 2: Triz (Genrich Altshuller): Do not compromise. If you face a trade-off (e.g., strength vs. weight), use dialectic logic to resolve the contradiction entirely. Aim for the “Ideal Final Result” (function without cost)[11].
• Methodology 3: Hierarchic Decomposition (Simon): Because the system is “nearly decomposable,” break it into “boxes-within-boxes” (subsystems) and optimize the short-run behavior of each part[12].
--------------------------------------------------------------------------------
Route 2: The Ecologist (Adaptation)
Context: Biological systems, Markets, Operations, Competitive Strategy.Goal: Viability, Resilience, and “Staying in the Game.”
• Methodology 1: The Viable System Model (Beer/Hoverstadt): Design for Requisite Variety. If the environment is too complex, you must either attenuate (filter) the incoming variety or amplify your own variety (e.g., through delegation or technology)[13][14].
• Methodology 2: Manage the Context (Allen): Do not micromanage the parts (N−1). Manage the Context (N+1). By replacing or subsidizing the missing context, the parts will self-organize to fit the new constraint[15][16].
• Methodology 3: Discover Constraints (Ladyman): If you cannot regulate the system, find the constraints that naturally reduce its variety. Use “middle-out” analysis rather than top-down control[17][18].
• Methodology 4: Scalable Abduction (Boisot): Instead of predicting, track “butterfly events” (tiny initiating signals) to see how they might amplify. Focus on agility over efficiency[19].
--------------------------------------------------------------------------------
Route 3: The Diplomat (Negotiation)
Context: Public Policy, Boards of Directors, “Wicked Problems,” Family Disputes.Goal: Accommodation, Learning, and “Procedural Justice.”
• Methodology 1: Soft Systems Methodology (Checkland): Abandon the idea of “problems” and “solutions.” Model the different Worldviews (Weltanschauungen) involved. Seek an “accommodation”—a version of the situation that conflicting parties can live with[20].
• Methodology 2: Problem Structuring (Eden): Use Cognitive Mapping and SODA to capture the “mess.” Focus on “Small Wins” and “procedural justice” (fairness in the process) to build emotional commitment[21][22].
• Methodology 3: Argumentation (Rittel): Accept that there is no “stopping rule” or correct answer. Treat the design process as an argumentative process to expose judgments. Settle for a “good enough” resolution[23].
• Methodology 4: Idealized Design (Ackoff): If the conflict is entrenched, assume the system was destroyed last night. Ask stakeholders to design the “Ideal System” from scratch. This often breaks deadlock by shifting focus from current complaints to future desires[24].
--------------------------------------------------------------------------------
Route 4: The Stabilizer (Crisis & Muddle)
Context: System collapse, panic, information overload, or “Runaway.”Goal: Stabilization and restoration of flexibility.
• Methodology 1: Budget of Flexibility (Bateson): Stop maximizing variables (e.g., speed/profit). Push variables back to the middle of their tolerable limits to restore the system’s “uncommitted potentiality for change”[25].
• Methodology 2: Strategic Nudges (TOG): Do not “boil the ocean.” Identify minimalist interventions or “constitutive rules” (changing the rules of the game) to stabilize the muddle without solving the whole[4][26].
• Methodology 3: Filter Complexity (Wilk): Use “Rule-out” questioning. Instead of modeling the whole, ask binary questions (“Is it in this half or that half?”) to logarithmically reduce the search space[27].
--------------------------------------------------------------------------------
Summary of the “Systemic Triage” Logic
| Step | Question | If NO… | If YES… |
|---|---|---|---|
| 1. Rosen Test | Is it a machine? (Simulable) | Go to Step 2 | Route 1: Engineer (Triz, Dettmer, Simon) |
| 2. Jackson Test | Do we agree on the goal? | Route 3: Diplomat (Checkland, Rittel, Eden) | Go to Step 3 |
| 3. Stability Test | Is it stable/viable? | Route 4: Stabilizer (Bateson, Wilk, TOG) | Route 2: Ecologist (Beer, Allen, Ladyman) |
References
[1] James Wilk.md [2] Robert Pirsig.md [3] Robert Pirsig.md [4] Mastering the Muddle - Systemic Perspectives on Complexity Management.md [5] Mastering the Muddle - Systemic Perspectives on Complexity Management.md [6] Relational Biologists - Robert Rosen Howard Pattee Dennis Noble.md [7] Tim Allen from Ecology.md [8] Horst Rittel.md [9] Theory of Constraints - William Dettmer.md [10] Theory of Constraints - William Dettmer.md [11] Triz.md [12] Herb Simon.md [13] Stafford Beer.md [14] Patrick Hoverstadt.md [15] Tim Allen from Ecology.md [16] Tim Allen from Ecology.md [17] James Ladyman and Ross Ashby.md [18] Relational Biologists - Robert Rosen Howard Pattee Dennis Noble.md [19] Max Boisot.md [20] Peter Checkland.md [21] Colin Eden and Fran Ackermann.md [22] Colin Eden and Fran Ackermann.md [23] Horst Rittel.md [24] Russ Ackoff.md [25] Gregory Bateson.md [26] TOG - Mastering the Muddle.md [27] James Wilk.md