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 Personas |  UX Research Customer Journey Mapping |  Product Discovery Smoke Test |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Tage | 2-4 h | 1-5 Tage | 45-60 min |
Participantsdifferent | Internes Team | 4-10 | Nutzertraffic | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Journey Map, Pain-point List, Opportunity Backlog | Interest Metrics, Conversion Signal, Learning Note | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ResearchCustomerSynthesis | JourneyServiceService design | ValidationExperimentsDemandGrowth | AssumptionsRiskExperimentsValidation |