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 |  Operations ABC Analysis |  UX Research Personas |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 30-60 min | 1-3 Tage | 45-90 min |
Participantsdifferent | 10-50 | 1-5 | Internes Team | 2-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Persona Profiles, Needs Summary, Scenario Notes | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | ResearchCustomerSynthesis | LeanProblem solvingCoachingOperations |