The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.
Evaporating Cloud
Explains a conflict through positions, needs, the shared objective, and the assumptions that keep the conflict in place.
Which conflict does the system maintain, which assumptions reinforce it, and which breakthroughs can resolve it?
First the two opposing demands are written down. Then their underlying needs and the shared objective are added. After that, the team checks the assumptions between the objective, the needs, and the demands and looks for a solution that disproves at least one of those assumptions.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Formulate the conflict positions
- 2Clarify the needs behind both sides
- 3Name the shared objective
- 4Collect stabilizing assumptions
- 5Derive breakthrough ideas
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Goal conflicts
- Organizational dilemmas
- Prioritization conflicts
Not good for
- Pure fact finding
- Acute escalation without willingness to talk
- Simple technical defects
Deep dive
The Evaporating Cloud treats conflicts not as a struggle between people, but as a logical tension between needs. Two incompatible wants are translated into the underlying needs and a shared objective. Then the assumptions that keep the conflict stable are tested. If an assumption is broken or changed, the conflict can disappear without a bad compromise.
Frame both sides fairly and avoid winner-loser language. Work cleanly from wants to needs and test assumptions explicitly. Good facilitation protects psychological safety because conflicts otherwise get personalized quickly.
Evaporating Cloud Working TemplateCompact working template for Evaporating Cloud with context, input, output artifacts, and next step.markdown
evaporating-cloud-working-template.md
Compact working template for Evaporating Cloud with context, input, output artifacts, and next step.
Evaporating Cloud Working Template
Goal
TOC method for resolving apparent conflicts through needs, assumptions, and breakthrough ideas.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Conflict Cloud:
- Assumption List:
- Breakthrough Ideas:
- Next Experiments:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Statt Evaporating Cloud, wenn ihr treibende und bremsende Kräfte einer Veränderung gegeneinander aufsetzen wollt.
Statt Evaporating Cloud, wenn ihr eine Gruppe nacheinander in unterschiedliche Denkmodi führen wollt.
Similar methods
All methodsTurns relationships, patterns, and leverage points into a tangible result by formulating the planned change, deriving desired effects, and refining and safeguarding the solution.
Turns relationships, patterns, and leverage points into a tangible result by collecting undesirable effects, modeling root causes, and deriving obstacles and implementation steps.
Turns relationships, patterns, and leverage points into a tangible result by describing the situation, identifying customers and actors, and deriving environmental boundaries and a root definition.
Turns relationships, patterns, and leverage points into a tangible result by collecting variables, drawing causal links, and discussing leverage points.
Clarifies connections, patterns, and leverage points by treating the issue as a polarity, naming the poles, and defining balance actions.
Turns relationships, patterns, and leverage points into a tangible result by setting system boundaries, collecting components, and deriving leverage points.