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 |  Product Discovery Jobs to Be Done |  Operations 5 Whys |
|---|---|---|---|---|
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. | When switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-240 min | 1-2 Tage | 1-3 Wochen | 15-30 min |
Participantsdifferent | 1-6 | 10-50 | 5-12 Interviews | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Kano Matrix, Feature Classes, Priority Themes | Job Stories, Outcome Statements, Opportunity List | Root cause notes, Countermeasures |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | SatisfactionPrioritizationCustomer | CustomerOutcomesNeeds | Root causeIncidentLeanProblem solving |