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 |  Innovation Lean Startup |  Systems Thinking Evaporating Cloud |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | Wochen bis Monate je Lernzyklus | 60-120 min | 45-60 min |
Participantsdifferent | 1-4 | 2-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | LeanStartupValidationMVP | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskExperimentsValidation |