View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Argument MappingArchitecture Decision RecordSoftware Architecture CanvasDecision Rights Mapping
| Criterion | ![]() Decision Making Argument Mapping | ![]() Architecture Architecture Decision Record | ![]() Architecture Software Architecture Canvas | ![]() Decision Making Decision Rights Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 15-45 min | 1-2 h | 90-180 min |
Participantsdifferent | 1-8 | 1-3 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | ADR File, Decision Log, Rationale | Architecture Canvas, Goals, Constraints, Quality Attributes | Decision Rights Matrix, Agreement |
Tagsno overlap | SensemakingDecisionRationale | ArchitectureRationaleDocumentationGovernance | CanvasArchitectureAlignmentWorkshop | DecisionGovernanceAlignmentResponsibility |



