View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Usability TestingSAAM (Software Architecture Analysis Method)Card SortingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  UX Research Usability Testing |  Architecture SAAM (Software Architecture Analysis Method) |  UX Research Card Sorting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-2 h je Session | Preparation, scenario analysis, and findings review; effort depends on scope | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Based on research question | Architecture experts and stakeholders for scenarios and weighting | Based on research question | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Content groups, Label set, IA hypotheses | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ValidationUXPrototype | ArchitectureChangeAnalysisComparisonQuality | Information architectureNavigationStructure | ArchitectureQualityRiskTradeoffsStakeholders |