View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Risk StormingUsability TestingAssumption SurfacingATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture Risk Storming |  UX Research Usability Testing |  Decision Making Assumption Surfacing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Low | Medium | Low | High |
Timedifferent | 60-90 min | 1-2 h je Session | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-12 | Based on research question | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Usability Issues, Severity List, Recommendations | Assumption List, Critical Assumptions, Learning Plan | 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 | RiskArchitectureWorkshopValidation | ValidationUXPrototype | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskTradeoffsStakeholders |