Evaporating Cloud

Definition

The Evaporating Cloud (also called a Conflict Cloud or Conflict Diagram) is one of TOC's Thinking Processes tools for precisely defining a problem as an unresolved conflict rather than a vague gap. It lays out a common objective (A) that requires two necessary conditions (B and C), where each condition seems to demand an action (D and D') that directly conflicts with the other. Rather than compromising between D and D', the method looks for the erroneous assumption underlying one of the arrows in the diagram — the belief that D is truly required to get B, for instance — and invalidates it, which "evaporates" the conflict instead of splitting the difference.

In the Book

Chapter 15 introduces the cloud through a concrete organizational example: to succeed (A), a company must be efficient (B), which creates pressure to centralize (D); but it must also be effective (C), which creates pressure to decentralize (D'). Centralizing too far breaks effectiveness (bureaucracy, slow decisions); decentralizing too far breaks efficiency (noncompliance, duplicated resources) — so organizations oscillate between the two rather than resolving the tension. The chapter then generalizes the method to three recurring conflicts every manager faces around continuous improvement: when to change (versus maintaining stability), what to change (versus not risking scarce resources on the wrong thing), and how to change (versus waiting for full consensus or full resourcing) — each stated as its own cloud with its own D, D', B, and C. The chapter's method is to interrogate each arrow directly — "why does D jeopardize C, why does D' jeopardize B, why are D and D' in conflict, and why is there no other way (E) to satisfy both B and C" — which is how the underlying assumption gets exposed and challenged rather than argued around.

Why It Matters

The Evaporating Cloud reframes a stuck disagreement as a diagnostic object: instead of treating two opposing camps as needing to negotiate a middle ground, it asks what belief makes the conflict seem necessary in the first place, and whether that belief is actually true. This is valuable wherever people have quietly accepted a trade-off as inherent to the situation — cost versus quality, speed versus safety, autonomy versus control — because it offers a disciplined way to ask whether the trade-off is a fact about the world or an artifact of an unexamined assumption.