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 |  Operations Process Mapping |  Domain Modeling Context Map |  Operations After-Action Review |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen | 1-3 h | 1-3 h | 20-45 min |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Process Map, Handoff List, Improvement Backlog | Context Map, Integration Patterns, Boundary Notes | Lessons learned, Action items, Event summary |
Tagsno overlap | UX researchObservationContext | ProcessOperationsImprovement | Domain-Driven DesignBoundariesStrategy | LearningOperationsImprovement |