View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  UX Research Empathy Mapping |  Knowledge Modeling Event Modeling |  UX Research Personas |
|---|---|---|---|---|
Purposedifferent | 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 lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 30–60 min | 2-6 h | 1-3 Tage |
Participantsdifferent | 10-50 | 4-8 | 2-8 | Internes Team |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Empathy Map, Assumptions List, Research Gaps | Event Model, UI Flow, Commands, Read Models | Persona Profiles, Needs Summary, Scenario Notes |
Tagsno overlap | SatisfactionPrioritizationCustomer | SynthesisQualitativeWorkshop | EventsBlueprintDomain-Driven DesignBehavior | ResearchCustomerSynthesis |