View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordSpecification by ExampleArchitecture Communication CanvasExample Mapping
| Criterion |  Architecture Architecture Decision Record |  Agile Specification by Example |  Architecture Architecture Communication Canvas |  Agile Example Mapping |
|---|---|---|---|---|
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. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 60-90 min pro Feature | 60-120 min | 30-60 min |
Participantsdifferent | 1-3 | 3-6 | 2-8 | 3-7 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement |