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 Jobs to Be Done |  Product Discovery Kano Model |  Engineering Fault Isolation |
|---|---|---|---|---|
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 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. | 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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-240 min | 1-3 Wochen | 1-2 Tage | 30-180 min |
Participantsdifferent | 1-6 | 5-12 Interviews | 10-50 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Job Stories, Outcome Statements, Opportunity List | Kano Matrix, Feature Classes, Priority Themes | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | CustomerOutcomesNeeds | SatisfactionPrioritizationCustomer | TroubleshootingDiagnosisEngineering |