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 | ![]() Operations Gemba Walk | ![]() Agile Example Mapping | ![]() UX Research Contextual Inquiry |
|---|---|---|---|---|
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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 30-120 min | 30-60 min | 1-3 Wochen |
Participantsdifferent | 3-10 | 2-6 | 3-7 | 4-12 Beobachtungen |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Context canvas, Open questions, Shared context notes | Observation Notes, Improvement Ideas | Example Map, Acceptance Criteria, Open Questions | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | ContextFramingRequirementsCanvas | LeanObservationProcessOperations | Behavior-Driven DevelopmentRequirementsExamplesRefinement | UX researchObservationContext |



