View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Product Discovery Kano Model |  Operations A3 Problem Solving |
|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 30-240 min | 1-2 Tage | 45-90 min |
Participantsdifferent | 1-6 | 10-50 | 2-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Kano Matrix, Feature Classes, Priority Themes | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | SatisfactionPrioritizationCustomer | LeanProblem solvingCoachingOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
