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 A3 Problem Solving |  Domain Modeling Context Map |  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 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | Medium | Low |
Timedifferent | 1-2 Tage | 45-90 min | 1-3 h | 30-60 min |
Participantsdifferent | 10-50 | 2-5 | 2-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | A3 Report, Action Plan, Root Cause Analysis | Context Map, Integration Patterns, Boundary Notes | ABC Classification, Focus Rules, Control List |
Tagsno overlap | SatisfactionPrioritizationCustomer | LeanProblem solvingCoachingOperations | Domain-Driven DesignBoundariesStrategy | PrioritizationOperationsPortfolio |