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 Strategy RICE Scoring |  Product Discovery Kano Model |  Operations Root Cause Analysis |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
Purposedifferent | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-90 min | 1-2 Tage | 1-4 h | 1-3 h |
Participantsdifferent | 2-10 | 10-50 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RICE Scores, Ranked List, Assumption Log | Kano Matrix, Feature Classes, Priority Themes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | PrioritizationScoringRoadmapTradeoffs | SatisfactionPrioritizationCustomer | Root causeProblem solvingQualityIncident | Root causeTreeIncidentQuality |