View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Domain Modeling Domain Context Map | ![]() Operations Gemba Walk | ![]() UX Research Contextual Inquiry | ![]() Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 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 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 | Medium |
Timedifferent | 1-3 h | 30-120 min | 1-3 Wochen | 1-3 h |
Participantsdifferent | 3-10 | 2-6 | 4-12 Beobachtungen | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignContextBoundaries | LeanObservationProcessOperations | UX researchObservationContext | Domain-Driven DesignBoundariesModeling |



