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 |  Product Discovery Pretotyping |  Systems Thinking Future Reality Tree |  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. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 60-120 min | Stunden bis wenige Tage | 2-4 h | 45-60 min |
Participantsdifferent | 2-8 | 1-4 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ValidationDemandMVP | Theory of ConstraintsSystems thinkingChange | AssumptionsRiskExperimentsValidation |