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 | ![]() Delivery Cost of Delay | ![]() 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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 | 90-180 min | 1-2 Tage |
Participantsdifferent | Internes Team | 3-8 | 10-50 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | CoD Table, Prioritization Sequence | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | ResearchCustomerSynthesis | PrioritizationDeliveryEconomicsDecision | SatisfactionPrioritizationCustomer |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






