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 ExampleC4 ModelArchitecture Communication Canvas
| Criterion |  Architecture Architecture Decision Record |  Agile Specification by Example |  Architecture C4 Model |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 60-90 min pro Feature | 1-4 h | 60-120 min |
Participantsdifferent | 1-3 | 3-6 | 1-5 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests | Context Diagram, Container Diagram, Component Diagram | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationVisualization | ArchitectureCommunicationStakeholdersCanvas |