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 Context Map |  Domain Modeling Domain Context Map |  Operations Gemba Walk |  UX Research Contextual Inquiry |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 30-120 min | 1-3 Wochen |
Participantsdifferent | 2-8 | 3-10 | 2-6 | 4-12 Beobachtungen |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | Observation Notes, Improvement Ideas | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | LeanObservationProcessOperations | UX researchObservationContext |