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 |  Engineering Failure Scenario Analysis |  Decision Making Constraint Analysis |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | 1-3 h | 30-90 min | 45-60 min |
Participantsdifferent | 2-8 | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | FailureResilienceRisk | ConstraintsDecisionPlanningOptions | AssumptionsRiskExperimentsValidation |