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 | ![]() UX Research Affinity Diagramming | ![]() Product Discovery Assumption Mapping | ![]() Product Discovery Smoke Test |
|---|---|---|---|---|
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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 45–90 min | 45-60 min | 1-5 Tage |
Participantsdifferent | 1-4 | 3-10 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Theme clusters, Insight statements, Opportunity areas | Assumption map, Test backlog, Risk ranking | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ValidationDemandMVP | SynthesisQualitativeRoot cause | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandGrowth |



