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 Tree Testing | ![]() UX Research Card Sorting |
|---|---|---|---|
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 a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage | 20-45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | Based on research question | Based on research question |
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 | Findability Metrics, Path Analysis, Revised IA | Content groups, Label set, IA hypotheses |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Information architectureNavigationFindability | Information architectureNavigationStructure |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






