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 TroubleshootingATAM (Architecture Tradeoff Analysis Method)Kepner-TregoeFishbone Diagram
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Kepner-Tregoe |  Operations Fishbone Diagram |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 30-240 min | Several meetings plus preparation and analysis; total effort depends on scope | 2-8 h | 30-60 min |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Analysis, Decision Analysis, Risk Plan | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders | Problem solvingRoot causeDecisionOperations | Root causeQualityOperations |