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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.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
LowLowMediumMedium
Timedifferent
15-45 min1-2 h1-3 h1-4 h
Participantsdifferent
1-33-102-83-8
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesCause Tree, Evidence Notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
Root causeTreeIncidentQuality
Root causeProblem solvingQualityIncident
Add more methods