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 |  Agile Acceptance Criteria Workshop |  Operations A3 Problem Solving |  Agile Example Mapping |
|---|---|---|---|---|
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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 Tage | 20-40 min pro Story | 45-90 min | 30-60 min |
Participantsdifferent | 10-50 | 3-6 | 2-5 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Acceptance Criteria, Story Update | A3 Report, Action Plan, Root Cause Analysis | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | SatisfactionPrioritizationCustomer | AgileRequirementsRefinementBehavior-Driven Development | LeanProblem solvingCoachingOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement |