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 Card Sorting | ![]() Product Discovery Smoke Test | ![]() 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 content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 20-45 min | 1-5 Tage | 45-60 min |
Participantsdifferent | 1-4 | Based on research question | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Content groups, Label set, IA hypotheses | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationDemandMVP | Information architectureNavigationStructure | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation |



