Site Logo

STPrism

What is the gist

6 min read

What is the gist and principles behind this collection?

The gist of this collection is a dialectic inquiry into the stagnation of Systems Thinking (ST) as a discipline. It is a transcript of a massive, collaborative discussion initiated by Henry Kwok on the “Systems Thinking World” LinkedIn group, exploring why the adoption rate of systems thinking is “painfully slow” and questioning if the discipline is merely a “fad”[1].

The principles behind the collection are not a unified manifesto, but rather a series of competing and converging perspectives on why humans struggle to think systemically.

The Gist: Why Systems Thinking Fails to Launch

The participants collectively identify several root causes for the resistance to and slow uptake of systems thinking:

• Fragmentation and “Turf Wars”: The discipline is fractured into too many “schools” (System Dynamics, Viable System Model, Soft Systems Methodology, Critical Systems Heuristics, etc.). Newcomers are confused by the competing methodologies and acronyms, leading to a lack of a coherent identity for the field[2][3].

• The “Marketing” Problem: The language of ST is often alienating, academic, or mechanistic. Terms like “systems” can sound cold or dehumanizing to the layperson[4][5]. As participant Barry Landis notes, “Systems Thinking is OFFENSIVE to some people… [it] sounds like ‘thinking like a system’ and brings to mind ‘thinking like a computer system’“[4].

• Cognitive and Educational Barriers: The human brain and Western educational systems are wired for reductionism (breaking things into parts) and linear cause-and-effect logic. Thinking in loops, delays, and webs of relationships requires a cognitive shift that is difficult to teach and maintain[3].

• The Threat to Power: Systems thinking is inherently threatening to traditional management hierarchies. By exposing the lack of control leaders actually have over complex systems, ST undermines the “illusion of control” that executives and politicians rely on for authority[7][9]. As Gerrit Van Wyk notes, “The weakest link of systems thinking is human beings… Without us, complex systems work just fine”[10].

• Lack of Practicality: There is a perception that ST remains trapped in “ivory tower” theorizing. Practitioners struggle to translate abstract concepts (like “holism” or “emergence”) into concrete tools that solve immediate business problems like cash flow or hiring[11].

Key Principles and Debates

The discussion oscillates between several foundational principles that define the participants’ worldviews:

1. The Map vs. The TerritoryA recurring principle is the distinction between reality and our models of it. Citing Alfred Korzybski’s dictum “the map is not the territory,” participants argue that all models are simplifications and inherently “wrong,” though some are useful[14]. A central tension in the discussion is whether systems thinkers become so obsessed with their “maps” (diagrams, causal loops) that they lose touch with the “territory” (reality)[17][18].

2. Hard vs. Soft SystemsThe collection highlights a divide between:

• Hard Systems: Rooted in engineering and mechanics, focusing on optimization, inputs/outputs, and solving well-defined problems (e.g., fixing a car engine or a production line)[3][19].

• Soft Systems: Rooted in sociology and psychology, focusing on “messy,” ill-defined problems where human values, politics, and worldviews dominate (e.g., healthcare reform or organizational culture)[3].The consensus among many participants is that “hard” tools are often inappropriately applied to “soft” human problems, leading to failure[19].

3. Complexity vs. ComplicatedA critical distinction is drawn between complicated systems (like a Boeing 747), which are knowable and fixable by experts, and complex systems (like a rainforest or a corporation), which are emergent, self-organizing, and unpredictable[21][22]. Participants argue that treating complex systems as if they were merely complicated (a “machine model”) is a primary reason for the failure of management interventions[23][24].

4. Purpose and DefinitionThere is a fundamental disagreement on the definition of a system.

• The Realists: Some, like Darius Lecointe, argue for a rigid definition based on Ludwig von Bertalanffy, viewing systems as objective entities (often closed) that exist regardless of the observer[25][26].

• The Constructivists: Others, like Peter Bednar and Gene Bellinger, argue that a “system” is a subjective mental construct—a boundary drawn by an observer to make sense of the world. In this view, systems do not exist “out there”; they exist in the mind of the stakeholder[27][28].

5. The Role of the ObserverA recurring principle is Second-Order Cybernetics—the idea that the observer is part of the system they are observing. Objectivity is viewed as a myth[29]. Therefore, systems thinking must include self-reflection on one’s own biases, values, and assumptions[20][30].

Summary of the Resolution

The discussion does not conclude with a single solution but coalesces around the idea that Systems Thinking is not a methodology (a checklist of steps) but a worldview or a way of being[31][32]. To increase adoption, the group suggests moving away from jargon and “evangelizing” models, and instead focusing on facilitating “aha!” moments where people naturally discover the interconnectedness of their own reality[33][34].

Graph View