methodatlas
Method guideSystems Thinking

Evaporating Cloud

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium
Time60-120 min
Participants2-8
FormatWorkshop
MaturityEstablished
Plan Evaporating Cloud
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Choose one recurring conflict with two apparently incompatible actions and a shared goal.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

Conflict case, cloud A/B/C/D/D′, assumption cards, and injection log

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Conflict case, cloud A/B/C/D/D′, assumption cards, and injection log

People / roles

Cloud facilitator · representatives of both sides · goal owner · injection owner

Pre-read

Choose one recurring conflict with two apparently incompatible actions and a shared goal.

Time needed

60–120 minutes per core conflict.

Setup

Prepare a workspace with Demands · Needs · Goal · Assumptions · Injection; separate example from live data.

03

Core question

The one question this method answers

Which assumption sustains the apparent conflict between two legitimate needs, and which injection resolves it without compromise?

04

Flow

Phases with goal, actions, output and pitfall

The Evaporating Cloud makes both goals, their underlying needs, and a shared higher purpose explicit. Tested assumptions support an injection that resolves the conflict rather than merely compensating for it.

Evaporating Cloud · working structure

Fictional example

Fictional values show the actual method fields.

D and D′

State opposing prerequisites D and D′ as concrete actions.

D promise express anytime; D′ promise express only in capacity windows.

B and C

Identify necessary need B or C beneath each demand.

B fast customer commitment; C stable safe warehouse flow.

Shared goal

Phrase shared goal A for which both needs are necessary.

A reliable pickup with strong customer retention.

Assumption map

Make assumptions behind every necessity and conflict arrow explicit and challenge them.

D needed for B because customers only see anytime as fast; data show accepted 30-minute windows.

Win-win injection

Develop an injection that breaks an assumption and preserves B and C; test side effects.

Capacity-visible express windows plus emergency slot provide fast commitment and stable flow.

All values are fictional.

Reference · original teaching example

  1. 1

    Demands

    D and D′

    Goal

    D and D′: State opposing prerequisites D and D′ as concrete actions.

    Inputs for this step

    • Choose one recurring conflict with two apparently incompatible actions and a shared goal.
    • Conflict case, cloud A/B/C/D/D′, assumption cards, and injection log

    Actions

    • State opposing prerequisites D and D′ as concrete actions.

    Output

    D and D′

    State opposing prerequisites D and D′ as concrete actions.

    Quality check

    Are they truly incompatible and within influence?

    Pitfall

    One side is framed as the problem. Write both demands neutrally as actions.

    Timing: 15–20 minutes

  2. 2

    Needs

    B and C

    Goal

    B and C: Identify necessary need B or C beneath each demand.

    Inputs for this step

    • D and D′

    Actions

    • Identify necessary need B or C beneath each demand.

    Output

    B and C

    Identify necessary need B or C beneath each demand.

    Quality check

    Are needs legitimate and distinct from demands?

    Pitfall

    Positions are merely reworded. Ask repeatedly why each demand is necessary.

    Timing: 15–25 minutes

  3. 3

    Goal

    Shared goal

    Goal

    Shared goal: Phrase shared goal A for which both needs are necessary.

    Inputs for this step

    • B and C

    Actions

    • Phrase shared goal A for which both needs are necessary.

    Output

    Shared goal

    Phrase shared goal A for which both needs are necessary.

    Quality check

    Do B and C support the same measurable goal?

    Pitfall

    Goal is an empty consensus statement. Tie goal to system performance and affected people.

    Timing: 10–15 minutes

  4. 4

    Assumptions

    Assumption map

    Goal

    Assumption map: Make assumptions behind every necessity and conflict arrow explicit and challenge them.

    Inputs for this step

    • Shared goal

    Actions

    • Make assumptions behind every necessity and conflict arrow explicit and challenge them.

    Output

    Assumption map

    Make assumptions behind every necessity and conflict arrow explicit and challenge them.

    Quality check

    Is at least one concrete falsifiable assumption visible per arrow?

    Pitfall

    Cloud is discussed without assumptions. Add “because we assume…” and seek evidence.

    Timing: 20–35 minutes

  5. 5

    Injection

    Win-win injection

    Goal

    Win-win injection: Develop an injection that breaks an assumption and preserves B and C; test side effects.

    Inputs for this step

    • Assumption map

    Actions

    • Develop an injection that breaks an assumption and preserves B and C; test side effects.

    Output

    Win-win injection

    Develop an injection that breaks an assumption and preserves B and C; test side effects.

    Quality check

    Does it preserve both needs through a testable mechanism?

    Pitfall

    Compromise halves both demands. Break a specific assumption and test injection in an FRT.

    Timing: 20–30 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Evaporating Cloud · TOC-KonfliktdiagrammGegensätzliche Positionen über gemeinsames Ziel, Bedürfnisse und stabilisierende Annahmen auflösbar machen
Evaporating CloudDas Visual zeigt ein TOC-Konfliktdiagramm mit gemeinsamem Ziel, zwei Bedürfnissen, zwei gegensätzlichen Positionen, Annahmen und einem Durchbruchspunkt.Einen Zielkonflikt über Bedürfnisse und Annahmen auflösenDie Cloud trennt Positionen von Bedürfnissen und sucht die Annahme, deren Veränderung den Konflikt verschwinden lässt.damitdamitweil wir glaubenweil wir glaubenscheinbar unvereinbarWants sind sichtbar, Needs werden verhandelbarKonflikt verschwindet, wenn eine Annahme nicht mehr giltA · Gemeinsames Zielbeide Seiten wollen dasselbeübergeordnete ErgebnisB · Bedürfniswas Seite 1 schützen mussC · Bedürfniswas Seite 2 schützen mussD · Positionkonkreter Wunsch AD' · Positionkonkreter Wunsch BAnnahme brechenneue Option ohne faulen Kompromiss
Form

Evaporating Cloud with A/B/C/D/D′, tested necessity assumptions, and justified injection.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • Cloud diagram
  • Assumption cards
  • Injection test

evaporating-cloud-working-template.md

Set subject, evidence, roles, flow, and review.

Evaporating Cloud: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 60–120 minutes per core conflict.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Conflict case, cloud A/B/C/D/D′, assumption cards, and injection log
  • Roles: Cloud facilitator · representatives of both sides · goal owner · injection owner
  • Advance information: Choose one recurring conflict with two apparently incompatible actions and a shared goal.
  • Overall time needed: 60–120 minutes per core conflict.
  • Setup: Prepare a workspace with Demands · Needs · Goal · Assumptions · Injection; separate example from live data.

Prepare for the work steps

Demands: D and D′

  • Choose one recurring conflict with two apparently incompatible actions and a shared goal.
  • Conflict case, cloud A/B/C/D/D′, assumption cards, and injection log

Needs: B and C

  • D and D′

Goal: Shared goal

  • B and C

Assumptions: Assumption map

  • Shared goal

Injection: Win-win injection

  • Assumption map

Evaporating Cloud · working structure

D and D′

State opposing prerequisites D and D′ as concrete actions.

...

B and C

Identify necessary need B or C beneath each demand.

...

Shared goal

Phrase shared goal A for which both needs are necessary.

...

Assumption map

Make assumptions behind every necessity and conflict arrow explicit and challenge them.

...

Win-win injection

Develop an injection that breaks an assumption and preserves B and C; test side effects.

...

The blank worksheet contains prompts only.

Reference · original teaching example

Demands: D and D′

Expected artifact: D and D′

State opposing prerequisites D and D′ as concrete actions.

Entry:

...

  • Are they truly incompatible and within influence?

Needs: B and C

Expected artifact: B and C

Identify necessary need B or C beneath each demand.

Entry:

...

  • Are needs legitimate and distinct from demands?

Goal: Shared goal

Expected artifact: Shared goal

Phrase shared goal A for which both needs are necessary.

Entry:

...

  • Do B and C support the same measurable goal?

Assumptions: Assumption map

Expected artifact: Assumption map

Make assumptions behind every necessity and conflict arrow explicit and challenge them.

Entry:

...

  • Is at least one concrete falsifiable assumption visible per arrow?

Injection: Win-win injection

Expected artifact: Win-win injection

Develop an injection that breaks an assumption and preserves B and C; test side effects.

Entry:

...

  • Does it preserve both needs through a testable mechanism?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/evaporating-cloud/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

evaporating-cloud-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Evaporating Cloud · working structure

D and D′

D promise express anytime; D′ promise express only in capacity windows.

B and C

B fast customer commitment; C stable safe warehouse flow.

Shared goal

A reliable pickup with strong customer retention.

Assumption map

D needed for B because customers only see anytime as fast; data show accepted 30-minute windows.

Win-win injection

Capacity-visible express windows plus emergency slot provide fast commitment and stable flow.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. D and D′One side is framed as the problem.View in phase
  2. B and CPositions are merely reworded.View in phase
  3. Shared goalGoal is an empty consensus statement.View in phase
  4. Assumption mapCloud is discussed without assumptions.View in phase
  5. Win-win injectionCompromise halves both demands.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Demands: Are they truly incompatible and within influence?
Stop Needs: Are needs legitimate and distinct from demands?
Stop Goal: Do B and C support the same measurable goal?
Stop Assumptions: Is at least one concrete falsifiable assumption visible per arrow?
Stop Injection: Does it preserve both needs through a testable mechanism?

Method after Eliyahu M. Goldratt. Curated with 1 sources.

Sources: Evaporating Cloud

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree

Tests whether the found win-win injection actually leads to the desired effects.

Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping

Reframes a persistent tension behind the injection as a polarity with balancing actions.

View in playbookUnderstand a Systemic Problem and Find LeverageMove from a recurring symptom to the underlying system structure and a concrete leverage point.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods