View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Pretotyping |  Product Discovery Assumption Mapping |  Systems Thinking Evaporating Cloud |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 45-60 min | 60-120 min | 1-5 Tage |
Participantsdifferent | 1-4 | 2-8 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ValidationDemandMVP | AssumptionsRiskExperimentsValidation | Theory of ConstraintsAssumptionsSystems thinking | ValidationExperimentsDemandDiscovery |