Site Logo

STPrism

Conflict - Colin Eden

5 min read

Based on the provided sources, Colin Eden’s ideas (centered on Problem Structuring Methods, Cognitive Mapping, and “Small Wins”) contradict or conflict with several other authors who advocate for radical redesign, strict mathematical logic, or the rejection of abstract models.

Here are the specific ways Colin Eden’s ideas contradict or conflict with the other sources:

1. Intervention: “Small Wins” vs. “Idealized Design”

Eden’s strategy for managing uncertainty relies on incrementalism, which puts him at odds with the holistic designers.

• Colin Eden: Advocates for “Robust Action” in the form of “small incremental wins”[1]. He argues that because future states are impossible to define in radical uncertainty, organizations should focus on small, adaptable steps that foster learning and engagement[1].

• The Conflict (Ackoff & Ladyman):

 Russ Ackoff explicitly rejects the idea of piecemeal improvement. He advocates “Idealized Design”—assuming the system was “destroyed last night” and designing a perfect replacement from scratch—rather than inching forward from the current mess[2].     Philip Ladyman warns that when dealing with systemic failure, one must “reject incremental improvements” that merely treat symptoms. He argues for solutions that scale across the entire system rather than small wins[3].

2. Resolution: “Accommodation” vs. “The Ideal Final Result”

Eden’s focus on social negotiation conflicts with the engineering approaches that seek objective optimization.

• Colin Eden: Focuses on “Process Complexity” (managing diverse stakeholders)[4]. His goal is to achieve “emotional commitment” and “procedural justice” by finding options that different groups can live with, often implying compromise or accommodation[1].

• The Conflict (Triz & Dettmer):

Triz aims for the “Ideal Final Result” (performing a function with zero cost/complexity)[5]. It explicitly advises resolving contradictions entirely using dialectic logic, rather than compromising or navigating social “process” issues[5].

William Dettmer (TOC) uses “Logic Trees” (Current Reality Trees) to find the singular “hidden root cause”[6]. This contrasts with Eden’s view of “emergent understandings” and “messy” causal webs that require negotiation rather than a mathematical “destination finder”[1],[6].

3. Modeling: “Cognitive Maps” vs. “Video Descriptions”

Eden’s reliance on mapping mental models is directly challenged by authors who view such abstractions as barriers to truth.

• Colin Eden: Recommends “Cognitive Mapping” and “SODA” (Strategic Options Development and Analysis) to capture and structure the “thinking” and “intangibles” of various actors[4],[1]. He views these maps as essential to managing the “content complexity” of a problem[1].

• The Conflict (James Wilk):

James Wilk argues that trying to “model complexity” with “ad hoc maps… with boxes and arrows” is a failure[7]. He views “mid-level abstractions” (concepts often found in cognitive maps, like “staff attitudes”) as “conceptual smokescreens”[8].

Wilk prescribes climbing down the ladder of abstraction to get “video descriptions” (concrete, undeniable physical facts), whereas Eden climbs up into the mental frameworks and perceptions of stakeholders[9].

4. Simplification: “Chunking” vs. “Ignoring Variables”

While Eden uses clustering to manage views, he warns against losing richness, conflicting with those who advise ruthless filtering.

• Colin Eden: Advises “chunking” complex maps into clusters/themes to manage cognitive load[1], but simultaneously warns that “simplification can be dangerous” if it strips away the subtlety and richness of the real issue[1].

• The Conflict (TOG & Boisot):

TOG (Mastering the Muddle) argues that the hallmark of mastery is the “essential selection step”—knowing what to leave out[10]. It advises practitioners to “master the art of ignoring variables” rather than trying to map the richness of the whole[10].

Max Boisot advocates for “Complexity Reduction” via codification and abstraction to filter out “crude complexity” (noise), which conflicts with Eden’s desire to capture the “emergent understandings” and “perplexing uncertainties” in full detail[4],[11].

5. Definition: Social “Mess” vs. Physical “Randomness”

Eden’s definition of complexity is sociopolitical, which clashes with the physical/mathematical definitions.

• Colin Eden: Defines complexity largely through a social lens: “Process Complexity” (multiple stakeholders) and “Content Complexity” (intangibles and uncertainty)[4]. He associates complexity with “Grand Challenges” and “Wicked Problems”[12].

• The Conflict (Abel & Triz):

David L. Abel defines complexity mathematically as “randomness” and the “lack of order”[13]. He argues that complexity is “blind to function”[14], whereas Eden views complexity as a web of meaningful (though difficult) human associations and purposes.

Triz calculates complexity as a physical cost—the “expenditure of resources” (NC=∣m∣+∣n∣)—focusing on spatial and temporal parameters rather than the stakeholder relationships central to Eden’s work[15].

6. Information Management: “Participatory” vs. “Solitary”

Eden’s approach to gathering information contradicts the solitary, introspective methods proposed by Pirsig.

• Colin Eden: Emphasizes “Participatory Architectures” and “Group Support Systems” (GSS)[1]. He focuses on “safe spaces” for dialogue and “anonymous contributions” to ensure all voices are heard in a collective setting[1].

• The Conflict (Robert Pirsig):

Robert Pirsig advocates a solitary approach using a “Slip System” (index cards) to organize data[16]. He recommends “emptying the tea cup” (forgetting) and working alone to cultivate “peace of mind” and “stuckness”[17], rather than engaging in the noisy, multi-stakeholder workshops Eden prescribes.

Graph View