View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Context CanvasSpecification by ExampleArchitecture Decision RecordArchitecture Communication Canvas
| Criterion |  Product Discovery Context Canvas |  Agile Specification by Example |  Architecture Architecture Decision Record |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 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 | 45-90 min | 60-90 min pro Feature | 15-45 min | 60-120 min |
Participantsdifferent | 3-10 | 3-6 | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |