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 Future Reality Tree |  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. | 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. | A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | Stunden bis wenige Tage | Wochen bis Monate je Lernzyklus | 2-4 h | 60-120 min |
Participantsdifferent | 1-4 | 2-8 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Future Reality Tree, Negative Branches, Assumption List, Improved Injections | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | ValidationDemandMVP | LeanStartupValidationMVP | Theory of ConstraintsSystems thinkingChange | Theory of ConstraintsAssumptionsSystems thinking |