Use this when two sides of a decision seem locked in direct opposition — when "we can either do A or B, but not both" feels like an iron law. The
Conflict Resolution Diagram, also called the Evaporating Cloud, maps the hidden assumptions beneath each position and systematically invalidates them, turning apparent either/or deadlocks into solvable problems.
Section 1
What This Tool Does
Every organisation has conflicts that feel permanent. Ship fast or ship quality. Invest in growth or protect margins. Centralise for efficiency or decentralise for speed. These dilemmas recur in strategy meetings, board discussions, and founder arguments with a grinding regularity that suggests they're structural features of the business — tradeoffs baked into the physics of the situation. Most teams respond by compromising: split the difference, give each side half of what it wants, revisit in six months. The compromise satisfies nobody, solves nothing, and the same argument resurfaces at the next offsite with slightly different vocabulary.
Eliyahu Goldratt saw this pattern everywhere he looked. A physicist by training who wandered into manufacturing consulting in the 1980s, Goldratt had an outsider's impatience with the way business people accepted contradictions. In physics, when two models predict contradictory outcomes, at least one model contains a flawed assumption. The contradiction isn't real — it's a signal that your understanding is incomplete. Goldratt applied this logic to organisational conflicts and built a tool he called the Evaporating Cloud, later formalised as the Conflict Resolution Diagram within his
Theory of Constraints framework. The name is precise: the conflict doesn't get resolved through negotiation or compromise. It evaporates — ceases to exist — once you find and invalidate the assumption that was making it appear real.
The mechanism is elegant. You map five elements: a shared objective both sides actually agree on, two necessary conditions (the needs each side is trying to protect), and two prerequisites (the specific actions each side insists on, which are in direct conflict). Then — and this is where the tool earns its keep — you surface the assumptions connecting each element to the next. Why does Need A require Action D? What would have to be true for that link to hold? The assumptions are usually unstated, often unconscious, and frequently wrong. The core insight: conflicts between intelligent people almost never stem from incompatible goals. They stem from unexamined assumptions about the only way to achieve those goals. When you find the faulty assumption and invalidate it, the conflict doesn't need to be managed. It disappears.
This is fundamentally different from negotiation, which accepts the conflict as real and seeks an acceptable distribution of losses. It's different from compromise, which gives each side less than it needs. And it's different from escalation, which lets a senior leader pick a winner. The Evaporating Cloud is the only common decision tool that treats the existence of the conflict itself as a diagnostic signal — evidence that someone, somewhere, is operating on a false premise.
The tool works because organisational conflicts are almost never about values. They're about logic chains. Two people who both want the company to succeed have constructed different causal models of how to get there, and at least one of those models contains an assumption that doesn't survive scrutiny. The diagram makes those models visible, comparable, and testable. That's the whole trick.
