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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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 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
1-2 h1-3 h15-45 min30-60 min
Participantsdifferent
3-101-81-32-10
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesArgument Map, Evidence Gaps, Decision RationaleADR File, Decision Log, RationaleDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
SensemakingDecisionRationale
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernanceAlignment
Add more methods