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 Fault Isolation |  Decision Making Force Field Analysis |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-180 min | 45-90 min | 30-240 min |
Participantsdifferent | 1-6 | 3-12 | 1-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Force Field Map, Change Levers, Risk Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ChangeDecisionStrategy | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
