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 PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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
Purposedifferent
For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
1 h bis mehrere Wochen1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope15-30 min
Participantsdifferent
1-83-8Evaluation team, architects, and relevant stakeholders2-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
PDCA Log, Experiment Plan, Learning Outcome, Standard ChangeProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRoot cause notes, Countermeasures
Tagsno overlap
Continuous improvementLeanExperiments
Root causeProblem solvingQualityIncident
ArchitectureQualityRiskTradeoffsStakeholders
Root causeIncidentLeanProblem solving
Add more methods