View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingA3 Problem SolvingArchitecture Decision RecordFault Isolation
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Operations A3 Problem Solving |  Architecture Architecture Decision Record |  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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-240 min | 45-90 min | 15-45 min | 30-180 min |
Participantsdifferent | 1-6 | 2-5 | 1-3 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | A3 Report, Action Plan, Root Cause Analysis | ADR File, Decision Log, Rationale | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | LeanProblem solvingCoachingOperations | ArchitectureRationaleDocumentationGovernance | TroubleshootingDiagnosisEngineering |