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 After-Action Review |  Domain Modeling Domain 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 20-45 min | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 3-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Lessons learned, Action items, Event summary | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | UX researchObservationContext | LearningOperationsImprovement | Domain-Driven DesignContextBoundaries |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
