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 |  Innovation Design Thinking |  UX Research Personas |  Operations ABC 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-2 Tage | 1 Tag bis mehrere Wochen | 1-3 Tage | 30-60 min |
Participantsdifferent | 10-50 | 4-10 | Internes Team | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Prototype, Test Learnings | Persona Profiles, Needs Summary, Scenario Notes | ABC Classification, Focus Rules, Control List |
Tagsno overlap | SatisfactionPrioritizationCustomer | InnovationPrototypeResearch | ResearchCustomerSynthesis | PrioritizationOperationsPortfolio |