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 Design Service Blueprinting |  Product Discovery Kano Model |  UX Research Customer Journey 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 service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit. | 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 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 Tage | 0.5-2 Tage | 1-2 Tage | 2-4 h |
Participantsdifferent | Internes Team | 6-12 | 10-50 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Service Blueprint, Fail Points, Ownership Map | Kano Matrix, Feature Classes, Priority Themes | Journey Map, Pain-point List, Opportunity Backlog |
Tagsno overlap | ResearchCustomerSynthesis | Service designOperationsJourneyBlueprint | SatisfactionPrioritizationCustomer | JourneyServiceService design |