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 Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.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
MediumLowMediumLow
Timedifferent
1-3 h15-45 min2-4 h15-30 min
Participantsdifferent
2-81-32-62-6
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Cause Tree, Evidence Notes, CountermeasuresADR File, Decision Log, RationaleBarrier Inventory, Failure Analysis per Barrier, Action BacklogRoot cause notes, Countermeasures
Tagsno overlap
Root causeTreeIncidentQuality
ArchitectureRationaleDocumentationGovernance
Root causeSafetyIncident
Root causeIncidentLeanProblem solving
Add more methods