Mess vs. Problem

Definition

A mess is a system of problems whose solution depends more on how the parts interact than on how each part behaves independently. Problems, by contrast, are abstractions extracted from experience—they appear separable and can theoretically be solved in isolation. Ackoff argues that organizations almost never face separable problems; they face messes. The difference is fundamental: you solve a problem, but you dissolve a mess.

In the Book

Ackoff defines messes early in Chapter 1 (around page 576): "Systems of problems... are called messes. The behavior of a mess depends more on how its parts interact than on how they act independently of each other." He contrasts this sharply with the standard practice of reducing messes to lists of problems, prioritizing them, and treating them separately—a practice he calls "reducing messes to lists of problems: to prioritize and treat them separately, as self-contained entities." His example of the General Electric refrigerator problem illustrates this perfectly. The company faced what seemed like an inventory problem (two door configurations, unpredictable demand mix), but the actual mess involved sales incentives, production constraints, customer expectations, and market variation all interacting. When GE focused narrowly on the "inventory problem" through forecasting, they failed; only when they tackled the underlying mess by redesigning the product did the problem dissolve. The paper-producing company's example shows how a production-management mess actually needed a sales-compensation solution: the mess spanned functions, not the traditional department where it appeared.

Why It Matters

Recognizing something as a mess rather than a problem changes how you approach it. It prevents the trap of solving the wrong thing—optimizing one part of a system while the system as a whole declines. Most organizational interventions fail because they treat messes as lists of separable problems. This concept lets you see when a problem is actually a symptom of a system-level misalignment, and when coordination across traditional boundaries is the only path forward. It's what makes systems thinking practical.