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 Personas |  Operations Root Cause Analysis |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
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 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-3 Tage | 1-4 h | 1-3 h |
Participantsdifferent | 10-50 | Internes Team | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Persona Profiles, Needs Summary, Scenario Notes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | SatisfactionPrioritizationCustomer | ResearchCustomerSynthesis | Root causeProblem solvingQualityIncident | Root causeTreeIncidentQuality |