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 |  Innovation Lean Startup |  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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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 | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage | 1-5 Tage |
Participantsdifferent | 2-8 | 2-8 | 1-4 | Nutzertraffic |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | LeanStartupValidationMVP | ValidationDemandMVP | ValidationExperimentsDemandDiscovery |