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 | ![]() Systems Thinking Future Reality Tree | ![]() Product Discovery Riskiest Assumption Test | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 60-120 min | 2-4 h | 1-2 Wochen pro Iteration | 1-5 Tage |
Participantsdifferent | 2-8 | 3-8 | 2-6 | Nutzertraffic |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Prioritized Assumption List, Test Plan, Results Report | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Theory of ConstraintsSystems thinkingChange | ExperimentsValidationDiscoveryAssumptions | ValidationExperimentsDemandDiscovery |



