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 Strategy Lean Canvas | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|
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 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 60-120 min |
Participantsdifferent | 1-4 | 1-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Lean Canvas, Core Assumptions, Experiment Backlog | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | ValidationDemandMVP | StartupLeanAssumptionsBusiness model | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






