View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Evaporating Cloud | ![]() Operations A3 Problem Solving | ![]() Systems Thinking Future Reality Tree | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 60-120 min | 45-90 min | 2-4 h | 15-30 min |
Participantsdifferent | 2-8 | 2-5 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | A3 Report, Action Plan, Root Cause Analysis | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Root cause notes, Countermeasures |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | LeanProblem solvingCoachingOperations | Theory of ConstraintsSystems thinkingChange | Root causeIncidentLeanProblem solving |



