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 |  UX Research HEART Framework |  Operations Root Cause Tree Analysis |  Operations Root Cause 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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 120 min initial, dann laufend | 1-3 h | 1-4 h |
Participantsdifferent | 10-50 | 3-6 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | HEART-GSM Table, Dashboard | Cause Tree, Evidence Notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | SatisfactionPrioritizationCustomer | MetricsUX researchMeasurementSatisfaction | Root causeTreeIncidentQuality | Root causeProblem solvingQualityIncident |