Systems Methodology: Self-Organization and Interactive Design
This is post 10 of 23 in a series on Systems Thinking: Managing Chaos and Complexity by Jamshid Gharajedaghi (ISBN: 978-0-7506-7973-2).
Previous: Systems Methodology - Holistic and Operational Thinking
In Part 1 we covered holistic thinking and operational thinking. Those were the first two foundations of systems methodology. Now we get to the other two: self-organization and interactive design. These are where things start getting really practical. If the first two foundations were about how to see the world, these two are about how to actually do something about it.
Self-Organization: Culture Is the Operating System
Gharajedaghi’s third foundation is self-organization. And the big idea here is that social systems move toward a predefined order. Not randomly. Not chaotically. They follow a blueprint. And that blueprint is culture.
Think about it like this. In biology, DNA tells a cell what to become. It carries the instructions. In social systems, the shared image, the collection of beliefs, values, attitudes, and assumptions that a group holds, does the same job. Culture is the DNA of an organization.
This is why change is so hard. You can redesign the org chart. You can write new policies. You can hire consultants. But if the shared image stays the same, the system will just regenerate the old pattern. Gharajedaghi calls this the “second-order machine.” It’s the set of cultural codes that keeps pulling the system back to its default state. It works like an attractor in chaos theory. No matter what you do on the surface, the system keeps drifting back to the same behavior.
That metaphor is actually really helpful. If you’ve ever worked somewhere that went through a big “transformation” only to end up doing the same things 18 months later, you’ve experienced the second-order machine in action.
Culture Does Two Things
Gharajedaghi says culture has two dimensions. First, there’s the cognitive side: language, meaning, how people think and reason. Second, there’s the normative side: values, beliefs, and social contracts.
Both matter. You can’t change how an organization behaves if you don’t address how people think AND what they believe is right. He compares culture to an operating system on a computer. Without an operating system, a computer is just a box of parts. Without a functioning culture, a social system is stuck.
This is a point that a lot of change management approaches miss. They focus on processes and structures. They forget that the people running those processes have deeply held assumptions about how things should work. Until you address those assumptions, nothing really changes.
The Viability Problem
Here’s where it gets interesting. Gharajedaghi says that for a culture to keep a system viable, it has to be capable of questioning its own assumptions. A system that can’t challenge its sacred beliefs is a system that can’t adapt.
He uses some strong real-world examples. Traditional societies that punish anyone who questions established practices are locked into patterns that block development. The freedom to question without fear isn’t just a nice-to-have. It’s a survival requirement for any social system.
He also talks about the butterfly effect in social systems. A small disturbance that connects with existing frustrations can amplify through feedback loops and produce massive change. But without addressing the underlying cultural codes, you can end up swapping one dysfunctional pattern for another. The collapse of the Soviet Union and Iran’s revolution are his examples. The old order broke down, but new forms of the same problems showed up because the deeper cultural codes weren’t reworked.
Interactive Design: Stop Predicting, Start Designing
The fourth foundation is interactive design, and Gharajedaghi credits Russell Ackoff as its primary architect. The core belief is simple: stop trying to predict the future and start designing it.
Interactive design rests on a few key assumptions that are worth stating clearly:
- The future isn’t locked in. Much of it hasn’t been written yet.
- The best way to understand a system is to redesign it.
- People accept ideas more easily when they helped create them.
- Big improvements need redesign, not just tweaks.
- You can build a feasible whole from individually unfeasible parts.
- Opposing needs can be both/and, not either/or.
That second-to-last one is my favorite. You can combine ideas that wouldn’t work alone into something that does. That’s a fundamentally different way of thinking.
Two Outputs: Define the Problem, Then Design the Solution
Interactive design has two distinct phases, and separating them is the whole point.
First: formulate the mess. This means defining the problem properly before you jump to solutions. Gharajedaghi says we fail more often because we solve the wrong problem than because we can’t solve the right one. And he identifies three common traps in how people define problems:
- Defining the problem as a deviation from the norm. This just reinforces the existing order, which might be the actual source of the problem.
- Defining the problem as a lack of resources. We never have enough time, money, or information. That’s always true. It doesn’t tell you what the actual problem is.
- Defining the problem in terms of a solution you already have. This one is everywhere. Accountants see cash flow problems. Engineers see engineering problems. We match situations to the tools in our bag and call it problem-solving.
That third trap is brutal. He shares a story about a client who said, “Why are you pressuring me to face this problem when you know I don’t have a solution for it?” The client literally wouldn’t look at a problem unless he already knew the answer. And honestly, most of us do some version of this.
Gharajedaghi uses a great Stafford Beer quote here: “Acceptable ideas are competent no more, but competent ideas are not yet acceptable.” We know the old solutions don’t work, but we’re not brave enough to try new ones.
A “mess” in this methodology isn’t just a bad situation. It’s a specific thing: the future that’s already baked into the current way of operating. It’s an early warning system. It shows you where your current trajectory leads if nothing changes. The best example Gharajedaghi gives? Das Kapital. Marx’s biggest contribution wasn’t his proposed solution. It was his problem definition.
Second: idealization and realization. Once you’ve defined the mess, you design the solution. Idealization starts with a wild premise: imagine the system was destroyed overnight and you get to rebuild it from scratch. Not science fiction. Your new design has to be technologically feasible, operationally viable, and capable of learning and adapting.
The design process is iterative. First iteration: define what properties you want. Second: sketch alternative designs. Third: integrate them into one design everyone can agree on. Then keep refining.
Realization is about actually implementing the design in the real world. Gharajedaghi breaks the constraints into three types:
- Type I: things you can’t change right now. You work around them and monitor them so you can incorporate the full design later when they’re removed.
- Type II: constraints that need time, money, and effort to remove. This is the heavy lifting. Redesigning products, processes, measurement systems.
- Type III: behavioral constraints. These are self-imposed. Resistance to change. Lack of buy-in. Fear of the unknown. This is where you have to dissolve the second-order machine.
Why This All Fits Together
The four foundations aren’t separate tools you pick from. They work together.
Holistic thinking gives you the right frame. Operational thinking gives you the tools to model complexity. Self-organization explains why systems resist change and how culture acts as the operating system. Interactive design gives you the method to actually redesign the system and its culture.
Gharajedaghi makes a point at the end that I think is underappreciated. Interactive design, done with real participation from the people in the system, is an irreversible process. It changes how people think. Even if the design document never gets fully implemented, the act of designing together permanently shifts the shared image. People who have seen what’s possible can’t unsee it.
And if even a design with no constraints can’t produce a good outcome, that tells you something important too. It means the problem is in the environment, not the system. Shift your focus outward.
That’s the full methodology. Four foundations. One integrated approach. In the next post, we start applying it. We’ll look at the first step of interactive design in practice: how to actually search for and define the mess.