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 |  Decision Making Argument Mapping |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | Stunden bis wenige Tage | 1-3 h | 1-3 h | 1-4 h |
Participantsdifferent | 1-4 | 3-12 | 1-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Argument Map, Evidence Gaps, Decision Rationale | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | ValidationDemandMVP | KnowledgeMappingRisk | SensemakingDecisionRationale | RiskDecisionSensemaking |