View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Design Customer Journey Canvas |  Agile Example Mapping |  Product Discovery Context Canvas |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When a journey needs to be understood across several phases, it arranges experience, touchpoints, and opportunities into one picture. It makes gaps and friction along the user path clear. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30-60 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Customer Journey Canvas, Pain Points, Experience Opportunities | Example Map, Acceptance Criteria, Open Questions | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests |
Tagsno overlap | JourneyCustomerService designCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development |