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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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 DACI
Decision Making
DACI
Purposedifferent
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min15-45 min1-2 h30-60 min
Participantsdifferent
1-61-33-102-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Decision Tree, Option Map, Assumption ListADR File, Decision Log, RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
DecisionTreeOptions
ArchitectureRationaleDocumentationGovernance
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernanceAlignment
Add more methods