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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Empathy Mapping
UX Research
Empathy Mapping
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing.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.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
HighLowHighLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope30–60 min1-6 Wochen60-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders4-84-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsEmpathy Map, Assumptions List, Research Gaps8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
SynthesisQualitativeWorkshop
QualityProblem solvingRoot cause
RiskArchitectureWorkshopValidation
Add more methods