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 MappingSpecification by ExampleArchitecture Communication CanvasArchitecture Decision Record
| Criterion | ![]() Decision Making Argument Mapping | ![]() Agile Specification by Example | ![]() Architecture Architecture Communication Canvas | ![]() Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | 60-120 min | 15-45 min |
Participantsdifferent | 1-8 | 3-6 | 2-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Argument Map, Evidence Gaps, Decision Rationale | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale |
Tagsno overlap | SensemakingDecisionRationale | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance |



