View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fishbone Diagram |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | Low | High | Medium |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-120 min |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 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 | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | Root causeQualityOperations | ArchitectureQualityRiskTradeoffsStakeholders | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
