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 |  Decision Making Pareto Analysis |  Agile Specification by Example |  Operations 8D 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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-2 Tage | 30-60 min | 60-90 min pro Feature | 1-6 Wochen |
Participantsdifferent | 10-50 | 1-6 | 3-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Pareto Chart, Top Causes, Focus List | Example Table, Acceptance Tests | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | PrioritizationQualityFocusRoot cause | AgileRequirementsExamplesBehavior-Driven Development | QualityProblem solvingRoot cause |