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 Fake Door Test |  Systems Thinking Current 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. | When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once. | 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 | High | Medium |
Timedifferent | 60-120 min | 1-5 Tage | 2-6 h | 45-60 min |
Participantsdifferent | 2-8 | Nutzertraffic | 3-8 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Click Data, Interest Signal, Learning Decision | Current Reality Tree, Core Problems, Intervention Ideas | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ValidationExperimentsDemandDiscovery | Systems thinkingRoot causeConstraintsCausality | AssumptionsRiskExperimentsValidation |