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 |  Agile Example Mapping |  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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Low | Medium |
Timedifferent | 1-2 Tage | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 10-50 | 1-5 | 3-7 | 2-5 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | ABC Classification, Focus Rules, Control List | Example Map, Acceptance Criteria, Open Questions | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationOperationsPortfolio | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanProblem solvingCoachingOperations |