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
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for DACI
Decision Making
DACI
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.In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.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
LowMediumLowLow
Timedifferent
15-45 min90-180 min1-2 h30-60 min
Participantsdifferent
1-34-123-102-10
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleDecision Rights Matrix, AgreementArchitecture Canvas, Goals, Constraints, Quality AttributesDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
DecisionGovernanceAlignmentResponsibility
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernanceAlignment
Add more methods