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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Affinity Diagramming
UX Research
Affinity Diagramming
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowHighMedium
Timedifferent
15-30 min45–90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
2-63-10Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresTheme clusters, Insight statements, Opportunity areasPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
SynthesisQualitativeRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Root causeProblem solvingQualityIncident
Add more methods