View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |  Agile Example Mapping |
|---|---|---|---|---|
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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 15-45 min | 20-40 min pro Story | 30-60 min |
Participantsdifferent | 3-10 | 1-3 | 3-6 | 3-7 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ContextFramingRequirementsCanvas | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |