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 Barrier Analysis |  Operations Root Cause Analysis |  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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Medium | Low |
Timedifferent | 60-120 min | 2-4 h | 1-4 h | 15-30 min |
Participantsdifferent | 2-8 | 2-6 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Root causeSafetyIncident | Root causeProblem solvingQualityIncident | Root causeIncidentLeanProblem solving |