Defining the Problem: Searching and Mapping the Mess

This is post 11 of 23 in a series on Systems Thinking: Managing Chaos and Complexity by Jamshid Gharajedaghi (ISBN: 978-0-7506-7973-2).

We’re now in Chapter 6, which is called “Defining the Problem.” And honestly, this might be the most practical chapter so far. Everything we’ve talked about up to this point (systems principles, holistic thinking, interactive design) leads here. This is where you actually start doing the work.

But here’s the twist. The work isn’t solving the problem. It’s figuring out what the problem actually is.

What Is a “Mess”?

Gharajedaghi has a specific word for the kind of problems systems thinkers deal with. He calls them messes. Not as slang. As a technical term. He borrowed it from Russell Ackoff.

A mess is a system of problems. Not a single problem you can isolate and fix. A tangled web of issues that are all connected to each other. You can’t touch one without touching the others. The mess is an emergent phenomenon. It comes from the interactions between the parts, not from any single part on its own.

Here’s what makes messes so frustrating. They regenerate. You fix one piece and the mess reforms around it. That’s because the mess is the natural consequence of the existing order. It’s what happens when the current system keeps doing what it’s been doing. The mess assumes nothing will change, and it fights hard to prove itself right.

Think about a company losing market share. Sales blames the product. Product blames the budget. Finance blames the sales projections. Everyone points at a different problem. But the real issue is how all of them interact. That’s the mess.

Why Problem Definition Is the Hardest Part

Most people skip right past problem definition. They see a symptom, assume it’s the cause, and start building solutions. And then they’re surprised when things don’t improve.

Gharajedaghi says the biggest obstructions aren’t out there in the world. They’re inside our own heads. Hidden assumptions. Mental models we don’t even know we have. These are the things that shape how we see reality and what we think is possible.

He lists three things a mess is NOT defined by:

1. Deviations from a norm (just because something is different doesn’t make it the problem)
2. Lack of resources like time, money, or information (throwing more resources at a mess won’t fix it)
3. Improper application of a known solution (the mess isn’t about doing the old thing wrong, it’s about needing a different thing entirely)

This is a big deal. Because most organizations define their problems exactly this way. “We don’t have enough budget.” “We need more people.” “If only we had better data.” Those aren’t problem definitions. Those are symptoms dressed up as explanations.

The real purpose of formulating the mess is to make the actual enemy visible. To show everyone involved why the system behaves the way it does, so they can stop arguing about surface-level stuff and start addressing what’s really going on.

Searching: How to Find the Real Problem

Once you accept that you’re dealing with a mess, you need a way to investigate it. Gharajedaghi calls this phase “searching.” It’s an iterative process with three types of inquiry.

Systems Analysis is the first one. You take a snapshot of the current system and its environment. Structures, functions, processes. Members, stakeholders, products, markets, core technology. You describe what exists without making judgments about it.

Obstruction Analysis is where you start looking for trouble. You examine five dimensions of the social system: power, knowledge, wealth, beauty, and values. For each one, you ask: what’s malfunctioning? Where is authority disconnected from responsibility? Where are the measurement systems broken? Where is the feedback loop too slow?

System Dynamics is about time. You look at the past (what critical events shaped the last ten years), the future (what plausible events could put you at a serious disadvantage), and pattern recognition (are there trends, cycles, or recurring behaviors?). You also look at the behavioral patterns of the key players. Are they acting rationally? Emotionally? Is culture driving decisions?

These three inquiries don’t happen once and done. They iterate. You go through them, pause, make sense of what you’ve found, and then go through again with sharper questions. Each cycle gets more specific.

One thing Gharajedaghi emphasizes: don’t get lost in the jungle of information. Generate enough to establish whether each variable actually matters. You’re not trying to collect everything. You’re trying to understand the right things.

Mapping the Mess: Seeing the Connections

After searching, you’ve got a big pile of obstructions. Now what?

This is where mapping comes in. You take all those individual findings and synthesize them into a few themes. Each theme is an emergent property of its group, not just a label. It needs to be clearly defined and backed by evidence, not based on one-off incidents.

The real test? When you present a theme to people who actually work in the system, they should have an “aha” moment. They should recognize it instantly.

Then you look at how the themes interact with each other. Gharajedaghi walks through an example of a product division losing ground to a competitor. Here’s how the mess flows:

A substitute product starts gaining acceptance. Product potency drops. Market demand decreases. The division’s identity is tied to its market niche, so the first reaction is denial. They issue exaggerated forecasts to protect themselves. Those forecasts turn out wrong, damaging credibility. Now there’s pressure to cut costs. But the real need is product redesign. The operational system can’t handle a redesign, so it patches the existing product instead. Costs go up, sales go down, and the competition gets more time to lock in their position. The cycle repeats.

This is a vicious circle. And you can only see it when you map the interactions between themes. If you only looked at one piece (say, the exaggerated forecasts), you’d try to fix the forecasting process. But that’s not the problem. The problem is the entire feedback loop.

Counterintuitive Behavior

Gharajedaghi reminds us of four properties of social systems that make mapping tricky:

1. A single cause can have multiple effects
2. Cause and effect are separated by time and space
3. Cause and effect can swap roles (circularity)
4. Once an effect exists, removing the cause doesn’t necessarily remove the effect

He uses smoking as an example. Smoking reduces anxiety and helps maintain weight (both good for the heart short-term), but damages arteries long-term. The body coats damaged arteries with cholesterol, which eventually causes blockages. So is cholesterol the villain, or just a defense mechanism responding to a deeper issue? Simple correlations between variables can be misleading.

The Second-Order Machine

There’s one more concept here that’s worth calling out. Gharajedaghi talks about the “second-order machine.” It’s the hidden mechanism inside a system that produces the mess. It’s not something anyone designed on purpose. It’s an unintended consequence of the existing order.

This second-order machine creates what he calls “Type II properties.” These are the things that create inertia, prevent change, and block improvement. If you want a real breakthrough in performance, you have to find this machine and take it apart.

Usually it comes down to a few deeply held assumptions that seem innocent but are actually running the show. The winning formula that used to work, pushed too far, in a game that has changed.

My Take

I’ve been in rooms where smart people spent months solving the wrong problem. Not because they were bad at problem-solving, but because nobody stopped to ask: “Wait, what exactly is the problem?”

The mess framework forces you to slow down, look at the whole picture, and name the real dynamics at play. It’s not fast. It’s not glamorous. But it’s the difference between treating symptoms and actually fixing things.

The mapping technique is especially useful. Drawing out how themes interact makes invisible dynamics visible. Once everyone can see the same picture, you can finally have a productive conversation about what to do.

Next time, we’ll cover the third phase of mess formulation: telling the story.

Previous: Systems Methodology - Self-Organization and Interactive Design

Next: Defining the Problem - Telling the Story