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 User Interviews |
|---|---|---|---|---|
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 teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 Tage | 0.5-2 Tage | 1-2 Tage | 30–60 min per interview |
Participantsdifferent | Internes Team | 6-12 | 10-50 | 1 participant per interview |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Service Blueprint, Fail Points, Ownership Map | Kano Matrix, Feature Classes, Priority Themes | Interview Notes, Themes, Insight Summary |
Tagsno overlap | ResearchCustomerSynthesis | Service designOperationsJourneyBlueprint | SatisfactionPrioritizationCustomer | QualitativeResearchCustomerDiscovery |