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 Root Cause Analysis |  Operations Change 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 1-4 h | 45-120 min |
Participantsdifferent | 10-50 | 3-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | SatisfactionPrioritizationCustomer | Root causeProblem solvingQualityIncident | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
