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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.
Complexitydifferent
LowHighLowHigh
Timedifferent
15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min1-6 Wochen
Participantsdifferent
2-6Evaluation team, architects, and relevant stakeholders1-64-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPareto Chart, Top Causes, Focus List8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
PrioritizationQualityFocusRoot cause
QualityProblem solvingRoot cause
Add more methods