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 |  Delivery MoSCoW |
|---|---|---|---|---|
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. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 Tage | 90-180 min | 1-2 Tage | 30-90 min |
Participantsdifferent | Internes Team | 3-8 | 10-50 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Persona Profiles, Needs Summary, Scenario Notes | CoD Table, Prioritization Sequence | Kano Matrix, Feature Classes, Priority Themes | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | ResearchCustomerSynthesis | PrioritizationDeliveryEconomicsDecision | SatisfactionPrioritizationCustomer | PrioritizationScopeDecision |