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 TestingATAM (Architecture Tradeoff Analysis Method)Affinity Diagramming8D Problem Solving
| Criterion |  UX Research Usability Testing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research Affinity Diagramming |  Operations 8D Problem Solving |
|---|---|---|---|---|
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 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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-2 h je Session | Several meetings plus preparation and analysis; total effort depends on scope | 45–90 min | 1-6 Wochen |
Participantsdifferent | Based on research question | Evaluation team, architects, and relevant stakeholders | 3-10 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Theme clusters, Insight statements, Opportunity areas | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | ValidationUXPrototype | ArchitectureQualityRiskTradeoffsStakeholders | SynthesisQualitativeRoot cause | QualityProblem solvingRoot cause |