View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Product Discovery Pretotyping |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-2 h | Stunden bis wenige Tage | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 1-8 | 1-4 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | ValidationDemandMVP | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |