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 |  Decision Making Cynefin Workshop |  Knowledge Modeling Knowledge Mapping |  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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. | 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 | 60-180 min | 1-3 h | 45-60 min |
Participantsdifferent | 1-4 | 4-20 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | ComplexitySensemakingDecision | KnowledgeMappingRisk | AssumptionsRiskExperimentsValidation |