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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 Tage | 0.5-2 Tage | 1-2 Tage |
Participantsdifferent | Internes Team | 6-12 | 10-50 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | Service Blueprint, Fail Points, Ownership Map | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | ResearchCustomerSynthesis | Service designOperationsJourneyBlueprint | SatisfactionPrioritizationCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






