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)Assumption Surfacing
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Decision Making Assumption Surfacing |
|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 30-240 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
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 | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskDecisionDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
