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) |  UX Research Affinity Diagramming |  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. | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 | 45–90 min | 45-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | 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 | Theme clusters, Insight statements, Opportunity areas | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | SynthesisQualitativeRoot cause | ChangeRoot causeTroubleshootingComparison |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
