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 |  Knowledge Modeling Knowledge Mapping |  Innovation Lean Startup |  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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. | 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 | 1-3 h | Wochen bis Monate je Lernzyklus | 45-60 min |
Participantsdifferent | 1-4 | 3-12 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | KnowledgeMappingRisk | LeanStartupValidationMVP | AssumptionsRiskExperimentsValidation |