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 for Solution Interview
Product Discovery
Solution Interview
Paper illustration for Risk Storming.
Architecture
Risk Storming
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)
Purposedifferent
When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation.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.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
MediumLowMediumHigh
Timedifferent
30-60 min je Interview60-90 min1-2 h je SessionSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
5-10 Interviews4-12Based on research questionEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Solution Feedback, Objection List, Validation NotesAnnotated Diagram, Prioritized Risk List, Action BacklogUsability 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 investigations
Tagsno overlap
ValidationInterviewsPrototype
RiskArchitectureWorkshopValidation
ValidationUXPrototype
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods