View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fault IsolationArchitecture Decision RecordRoot Cause AnalysisHypothesis-Driven Troubleshooting
| Criterion |  Engineering Fault Isolation |  Architecture Architecture Decision Record |  Operations Root Cause 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. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Medium |
Timedifferent | 30-180 min | 15-45 min | 1-4 h | 30-240 min |
Participantsdifferent | 1-6 | 1-3 | 3-8 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | ADR File, Decision Log, Rationale | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ArchitectureRationaleDocumentationGovernance | Root causeProblem solvingQualityIncident | TroubleshootingProblem solvingDiagnosis |