View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Usability Testing |  Product Discovery Smoke Test |  Product Discovery Pretotyping |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-2 h je Session | 1-5 Tage | Stunden bis wenige Tage | 45-60 min |
Participantsdifferent | Based on research question | Nutzertraffic | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Interest Metrics, Conversion Signal, Learning Note | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Assumption map, Test backlog, Risk ranking |
Tags1 shared | ValidationUXPrototype | ValidationExperimentsDemandGrowth | ValidationDemandMVP | AssumptionsRiskExperimentsValidation |