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 Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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.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.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
90-180 min1-3 h1-2 h15-45 min
Participantsdifferent
4-121-83-101-3
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Decision Rights Matrix, AgreementArgument Map, Evidence Gaps, Decision RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, Rationale
Tagsno overlap
DecisionGovernanceAlignmentResponsibility
SensemakingDecisionRationale
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
Add more methods