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 RecordContext CanvasAcceptance Criteria WorkshopArchitecture Communication Canvas
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Context Canvas |  Agile Acceptance Criteria Workshop |  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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | Low | Low | Medium |
Timedifferent | 15-45 min | 45-90 min | 20-40 min pro Story | 60-120 min |
Participantsdifferent | 1-3 | 3-10 | 3-6 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Context canvas, Open questions, Shared context notes | Acceptance Criteria, Story Update | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ContextFramingRequirementsCanvas | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas |