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 |  Domain Modeling Domain Context Map |  Operations After-Action Review |  Domain Modeling Context Map |
|---|---|---|---|---|
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 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 20-45 min | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 3-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Lessons learned, Action items, Event summary | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | LearningOperationsImprovement | Domain-Driven DesignBoundariesStrategy |