methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration for Risk Storming.
Architecture
Risk Storming
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 the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-2 h je SessionSeveral meetings plus preparation and analysis; total effort depends on scope4-5 Tage60-90 min
Participantsdifferent
Based on research questionEvaluation team, architects, and relevant stakeholders5-84-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Usability Issues, Severity List, RecommendationsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrototype, Test Findings, Decision RationaleAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ValidationUXPrototype
ArchitectureQualityRiskTradeoffsStakeholders
Design sprintPrototypeValidationInnovation
RiskArchitectureWorkshopValidation
Add more methods