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 Fishbone Diagram |  Operations Kepner-Tregoe |
|---|---|---|---|---|
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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-2 Tage | 1-4 h | 30-60 min | 2-8 h |
Participantsdifferent | 10-50 | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Fishbone Diagram, Cause Categories, Investigation Backlog | Problem Analysis, Decision Analysis, Risk Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | Root causeProblem solvingQualityIncident | Root causeQualityOperations | Problem solvingRoot causeDecisionOperations |