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 for Change Analysis.
Operations
Change Analysis
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree 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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowMediumMedium
Timedifferent
15-30 min45-120 min1-3 h
Participantsdifferent
2-62-62-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Root cause notes, CountermeasuresChange Matrix, Cause Hypotheses, Validation Questions, Action ListCause Tree, Evidence Notes, Countermeasures
Tags1 shared
Root causeIncidentLeanProblem solving
ChangeRoot causeTroubleshootingComparison
Root causeTreeIncidentQuality
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving