Connect to Change

Connect To Chnage report

How do the ideas in v2-combined help address the challenges in connect to change

Gemini said

The ideas in V2-Combined provide a rigorous theoretical and practical foundation to address the urgent systemic challenges outlined in the Connect to Change booklet. While the booklet highlights what needs to change—moving from siloed, wasteful construction projects to a “system of systems” that delivers long-term outcomes —the systems thinkers in the combined collection provide the how.

Here is how these frameworks address the specific challenges of the built environment:

1. Breaking Organizational and Sector Silos

The booklet identifies “sector silos” ranging from government departments to operators as a primary barrier to realizing the value of the built environment.

• Systemic Pluralism: M.C. Jackson argues that because social complexity is multidimensional, no single “expert” or methodology is sufficient. His System of Systems Methodologies (SOSM) provides a way to combine different approaches—such as using Soft Systems Methodology (SSM) to navigate cultural differences and Cybernetics to manage structural efficiency—to break down these silos.
• Negotiated Knowledge: Colin Eden and David Blockley suggest handling silos by externalizing implicit “mental models” into shared visual maps (Cause Maps or Hierarchical Process Models). This shifts the focus from “Marketing is right and HR is wrong” to a collaborative debate on whether the diagram accurately captures the system’s behavior.

2. Shifting from Outputs to Outcomes

A core demand of the booklet is focusing on improving long-term environmental, social, and economic outcomes rather than merely delivering the outputs of individual projects.

• Idealized Design: Russell Ackoff provides a specific method for this shift. Instead of incrementally improving a flawed status quo, his Idealized Design process forces stakeholders to plan backward from an ideal replacement system. This removes the historical and self-imposed constraints that currently prioritize “building new” over better management.
• The Fifth Discipline: Peter Senge emphasizes that “there is no outside”—the organization and its perceived environment are one system. By using Systems Archetypes (like Limits to Growth or Shifting the Burden), leaders can identify where symptomatic “quick fixes” in construction projects are actually eroding the fundamental health of the larger built environment.

3. Managing Information and Interoperability

The booklet notes that information is poorly connected, data management is inadequate, and limited interoperability hinders asset value.

• The I-Space: Max Boisot provides a framework for understanding how knowledge moves from uncodified “scanning” of problems to the “abstraction” and “diffusion” required for industry-wide interoperability. He highlights that for data to be useful, it must match the “requisite complexity” of the environment.
• The Viable System Model (VSM): Stafford Beer identifies that organizations fail when they lack the structural channels to communicate and filter complexity. His VSM outlines five critical functions (Operations, Coordination, Control, Intelligence, and Policy) that must exist at every level to ensure information flows are not lost in the hierarchy.

4. Shifting Mindset and Leadership Culture

The booklet calls for visionary, “boundary-spanning” leadership that embraces complexity and shifts the industry culture from individualism to collective endeavor.

• Action Learning: Reginald Revans argues that deep change only occurs when leaders admit ignorance and learn through “Questioning Insight” in peer groups (Sets). This “comrades in adversity” model creates the “boundary-spanning” capability needed to coordinate diverse stakeholders.
• Muddling Through: John Flach and others advocate for Abduction—a logic of discovery where leaders acknowledge that perfect prediction is impossible and instead use small, safe-to-fail experiments to learn and “muddle through” complex challenges.

---

Synthesis: Addressing the Built Environment “Mess”

Booklet Challenge	Systemic Response from V2-Combined
Siloed Decision-Making	Methodological Pluralism: Using different tools for technical vs. human problems.
Priority of “New Build”	Idealized Design: Starting with the desired outcome, not the current project.
Wasteful/Inefficient Approach	Variety Engineering: Designing filters to reduce noise and amplifiers to boost control.
Cost of Inaction is Too High	Precautionary Principle: Prioritizing resilience over optimization when ruin is a possibility.

Would you like me to map one of these specific methodologies (like the Viable System Model or Idealized Design) directly onto a current built environment project you are working on?

Can you produce an extended and comprehensive report of the v2-collection ideas in the style of Barbara Minto using a SCQA section

Gemini said

Executive Report: Navigating Complexity through Systemic Practice

SCQA: The Case for a Paradigmatic Shift

• Situation: Modern civilization has moved from managing physical substances (stone, wood, iron) to managing a world defined by a massive explosion of connectivity, information flow, and “organized complexity”. This is particularly evident in the built environment, which now functions as a complex “system of systems” rather than a series of independent construction projects.
• Complication: Our primary methods for management and problem-solving remain rooted in the “Newtonian Paradigm”—a 350-year-old reductionist mindset that assumes we can understand and control the whole by breaking it into isolated, predictable parts. In complex systems, this “analytical method” fails because it destroys the very interactions and emergent properties that define the system’s behavior. Consequently, we suffer from “Errors of the Third Kind”: solving the wrong problems precisely by drawing boundaries too narrowly.
• Question: How can we effectively manage, intervene in, and improve these “messes” (systems of strongly interacting problems) when traditional linear logic and top-down control lead to fragility, waste, and unintended consequences?.
• Answer: We must adopt a Systems Thinking and Complexity Science framework that shifts from “optimizing” parts to “learning” and “managing constraints” within the whole. This requires a move from the “Machine Age” of command-and-control to the “Systems Age” of adaptive, self-organizing viability.

---

I. The Foundational Logic: Complexity vs. Complication

To address the complication, we must first distinguish between systems that are merely “complicated” and those that are truly “complex”.

1. Complicated Systems (The Mechanical): These are like washing machines or jet engines; they have many parts, but they are linear, deterministic, and can be fully understood by dissection (analysis).

2. Complex Systems (The Organic): These are like cats or urban economies; they are characterized by non-linear interdependencies, emergence, and “opacity”. In these systems, cause and effect are not closely related in time and space, making them “non-simulable”—meaning they cannot be fully captured by an algorithm or a master blueprint.

Key Principle: “Only variety can absorb variety” (Ashby’s Law). A system must possess internal complexity that matches the variety of its environment to remain stable and viable.

II. Strategic Principles for Systemic Intervention

Effective intervention in complex “messes” relies on five core strategic pillars:

• Synthesis over Analysis: Instead of breaking things down, identify the larger containing whole. Explain the behavior of the whole first, then define the role of the parts within it to gain true understanding rather than just knowledge.

• Idealized Design (Backcasting): Do not incrementally improve the current flawed state. Design the ideal system you would build right now from scratch and then plan backward to the present.

• Managing the “Water” (Contextual Constraints): The “water” is the environment of implicit mental models, power dynamics, and physical constraints that hold a problem in place. Interventions must target the slow-moving context (Supply-Side Sustainability) rather than micromanaging high-frequency outputs.

• Redundancy of Functions (Democratic Structure): To handle turbulence, shift from “Redundancy of Parts” (bureaucracy, where people are replaceable gears) to “Redundancy of Functions” (self-managing groups where individuals have multiple skills and local autonomy).

• Recursive Viability: Structure organizations fractally using the Viable System Model (VSM). Ensure every level (from the site team to the national regulator) possesses the same five essential functions: Operations, Coordination, Control, Intelligence, and Policy.

III. The Cognitive Practice: Managing Perspectives and Uncertainty

Systems thinking is ultimately an “observer phenomenon”—an epistemological tool rather than just a scientific description.

1. Multiple Perspectives (T-O-P): Complex systems must be viewed through three lenses simultaneously: Technical (data/models), Organizational (power/culture), and Personal (individual intuition/morals).

2. Boundary Critique: Every system is an artificial boundary drawn by an observer. We must critically evaluate who benefits (clients) and who is marginalized (victims) by where we choose to draw that line.

3. Embracing Uncertainty (Via Negativa): Since perfect prediction in “Extremistan” is impossible, we should focus on Antifragility—building systems that benefit from shocks and volatility rather than trying to eliminate them. Knowledge is often best gained through subtraction (removing what is harmful/wrong) rather than trying to add new “positive” solutions.

IV. Recommended Action Protocol: The Learning Cycle

To implement these ideas, organizations should abandon “Project Management” for “Systemic Inquiring”:

• Explore: Map the “Rich Picture” of the mess, including conflicts and stakeholder “emotioning”.

• Probing (Safe-to-Fail): When cause and effect are only visible in retrospect, use small, parallel experiments to sense the system’s propensities before committing large-scale resources.

• Amplify/Dampen: Monitor feedback loops. If a probe generates a desirable pattern (Virtuous Cycle), amplify it; if it produces a harmful one (Vicious Cycle), dampen it immediately.

• Reflect and Reframe: Use every intervention as a “triggering question” to update mental models and “reset” the appreciative settings of the leadership.

---

Next Steps: Would you like me to use the Interpretive Structural Modeling (ISM) logic to prioritize the specific “Built Environment Connective” recommendations from the booklet based on their systemic aggravation levels?.

You said

Yes use ISM

Gemini said

To prioritize the recommendations in the Connect to Change booklet using Interpretive Structural Modeling (ISM), we must move beyond a simple list and identify the contextual relationships between these actions.

In ISM, we ask a relational question—such as “Does Recommendation A significantly aggravate (or enable) Recommendation B?”—to build a directed graph (digraph) that reveals the “logic” of the transformation.

Based on the systemic principles in V2-Combined, here is an ISM-informed prioritization of the booklet’s practical steps:

Level 1: The Foundations (The “Unmoved Movers”)

According to Warfield’s logic, these elements must be addressed first because they “aggravate” all other failures if left unresolved.

• Recommendation: Leadership Development Programs.

  • Systemic Logic: Without “systems leadership” that embraces complexity, the organizational culture cannot shift from “heroic individualism” to “collective endeavour”.

• Recommendation: Embed Systems Thinking in Curricula (Competencies).

  • Systemic Logic: You cannot regulate or manage a system you cannot model; therefore, industry-wide capability is a prerequisite for any meaningful review or policy change.

Level 2: The Structural Frameworks

Once leadership and capability are established, these “decision premises” can be built to constrain future behavior toward better outcomes.

• Recommendation: Develop Outcomes-Focused, Systems-Based Metrics.

  • Systemic Logic: Metrics define the “Measure of Performance.” If we use the wrong metrics, we commit an “Error of the Third Kind” by optimizing for project outputs rather than societal outcomes.

• Recommendation: Publicly Available Specification (PAS) / Frameworks.

  • Systemic Logic: This acts as a “System 2” coordination mechanism in the Viable System Model, preventing different sectors from “oscillating” or working at cross-purposes.

Level 3: The Operational Enablers

These elements facilitate the day-to-day “flow” of systemic change and data across boundaries.

• Recommendation: Develop an Information Platform.

  • Systemic Logic: This reduces the “variety mismatch” between the system and its environment by enabling “connected data” to improve resilience.

• Recommendation: Advance the “Built Environment Connective” (Networking).

  • Systemic Logic: This fosters “structural coupling” between different organizations, allowing them to co-evolve rather than just react to one another.

Level 4: The Strategic Oversight (The Outcome)

These recommendations represent the highest level of systemic maturity, where the built environment is managed as a “whole”.

• Recommendation: Commission a “Built Environment Systems Review”.

• Recommendation: Empower a Body with Policy Remit and Oversight.

  • Systemic Logic: These represent “System 5” (Policy) and “System 4” (Intelligence). They balance the needs of today with the adaptation required for the future, but they can only function effectively if the data (Level 3) and metrics (Level 2) are already in place.

---

Prioritization Digraph Summary

1. Direct Action (Top): Policy Oversight & Systems Review (Requires all levels below).

2. Facilitators (Middle): Shared Platforms, Interoperable Data, & Connectivity.

3. Constraints (Middle): Outcomes-Based Metrics & Industry Standards.

4. Drivers (Bottom): Systems Leadership & Education (The primary leverage points).

Next Step: Would you like to pick one of the “Bottom” drivers (Leadership or Education) and use the Theory of Constraints “Prerequisite Tree” to identify the specific obstacles to implementing it in your current organization?.