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) |  Product Discovery Test Card |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-2 h je Session | Several meetings plus preparation and analysis; total effort depends on scope | 20-35 min | 45-60 min |
Participantsdifferent | Based on research question | Evaluation team, architects, and relevant stakeholders | 1-5 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + 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 | Test Card with a pre-set threshold | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ValidationUXPrototype | ArchitectureQualityRiskTradeoffsStakeholders | ExperimentsValidationDiscoveryHypothesis | AssumptionsRiskExperimentsValidation |