View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Product Discovery Jobs to Be Done |  Domain Modeling EventStorming |  Product Discovery Kano Model |
|---|---|---|---|---|
Purposedifferent | 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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30-60 min | 1-3 Wochen | 2-8 h | 1-2 Tage |
Participantsdifferent | 1-5 | 5-12 Interviews | 5-12 | 10-50 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | Job Stories, Outcome Statements, Opportunity List | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | Kano Matrix, Feature Classes, Priority Themes |
Tagsno overlap | PrioritizationOperationsPortfolio | CustomerOutcomesNeeds | Domain-Driven DesignEventsDiscoveryWorkshop | SatisfactionPrioritizationCustomer |