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 |  Agile Example Mapping |  UX Research Contextual Inquiry |  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. | 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 work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | 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 | Medium | Medium |
Timedifferent | 45-90 min | 30-60 min | 1-3 Wochen | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 3-7 | 4-12 Beobachtungen | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Example Map, Acceptance Criteria, Open Questions | Field Notes, Workflow Insights, Pain Points | Example Table, Acceptance Tests |
Tagsno overlap | ContextFramingRequirementsCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement | UX researchObservationContext | AgileRequirementsExamplesBehavior-Driven Development |