View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Usability Testing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Growth A/B Testing |
|---|---|---|---|
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. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | High | High |
Timedifferent | 1-2 h je Session | Several meetings plus preparation and analysis; total effort depends on scope | 1-4 Wochen |
Participantsdifferent | Based on research question | Evaluation team, architects, and relevant stakeholders | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationUXPrototype | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
