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 | ![]() Innovation Lean Startup |
|---|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | 45-90 min | Stunden bis wenige Tage | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 2-8 | 1-6 | 1-4 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + 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 | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | StartupLeanAssumptionsBusiness model | ValidationDemandMVP | LeanStartupValidationMVP |



