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 Research Contextual Inquiry | ![]() Agile Example Mapping | ![]() Domain Modeling Bounded Context Canvas |
|---|---|---|---|
Purposedifferent | 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 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 a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 30-60 min | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 3-7 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Example Map, Acceptance Criteria, Open Questions | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | UX researchObservationContext | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Domain-Driven DesignBoundariesModeling |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






