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 CanvasArchitecture Decision RecordAcceptance Criteria WorkshopSpecification by Example
| Criterion |  Product Discovery Context Canvas |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 15-45 min | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 1-3 | 3-6 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | ContextFramingRequirementsCanvas | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |