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 ATAM (Architecture Tradeoff Analysis Method) |  Operations Ivy Lee Method |  Operations Change Analysis |
|---|---|---|---|
Purposedifferent | 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. | With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field. | 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 | High | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 5-10 min daily | 45-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Daily Priority List, Completion Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | PrioritizationProductivityExecution | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
