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)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.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.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.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
HighLowHighMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope15-30 min1-6 Wochen1-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-64-103-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRoot cause notes, Countermeasures8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Root causeIncidentLeanProblem solving
QualityProblem solvingRoot cause
Root causeProblem solvingQualityIncident
Add more methods