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 |  Systems Thinking Evaporating Cloud |  Systems Thinking Intervention Mapping |  Innovation Lean Startup |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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 | Low | Medium | High | Medium |
Timedifferent | Stunden bis wenige Tage | 60-120 min | 1-5 Tage | Wochen bis Monate je Lernzyklus |
Participantsdifferent | 1-4 | 2-8 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision |
Tagsno overlap | ValidationDemandMVP | Theory of ConstraintsAssumptionsSystems thinking | ChangeSystems thinkingCapability | LeanStartupValidationMVP |