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 Strategy Lean Canvas |  Product Discovery Pretotyping |  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. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 60-120 min | 45-90 min | Stunden bis wenige Tage | 1-5 Tage |
Participantsdifferent | 2-8 | 1-6 | 1-4 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Lean Canvas, Core Assumptions, Experiment Backlog | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | StartupLeanAssumptionsBusiness model | ValidationDemandMVP | ValidationExperimentsDemandDiscovery |