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 |  Product Discovery Kano Model |  Growth A/B Testing |  Product Discovery Smoke Test |
|---|---|---|---|---|
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 features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | 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. | 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 | Medium | Medium | High | Low |
Timedifferent | 1-3 Tage | 1-2 Tage | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | Internes Team | 10-50 | 1-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Kano Matrix, Feature Classes, Priority Themes | Experiment results, Decision log, Learning summary | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | ResearchCustomerSynthesis | SatisfactionPrioritizationCustomer | ExperimentsGrowthAnalyticsValidation | ValidationExperimentsDemandGrowth |