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 TroubleshootingFishbone DiagramATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Operations Fishbone Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 30-240 min | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-6 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Fishbone Diagram, Cause Categories, Investigation Backlog | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | Root causeQualityOperations | ArchitectureQualityRiskTradeoffsStakeholders |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
