View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Engineering Hypothesis-Driven Troubleshooting |  Operations 5 Whys |
|---|---|---|---|
Purposedifferent | 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 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 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 | Low | Medium | Low |
Timedifferent | 15-45 min | 30-240 min | 15-30 min |
Participantsdifferent | 1-3 | 1-6 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Root cause notes, Countermeasures |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TroubleshootingProblem solvingDiagnosis | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
