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 | ![]() UX Research Usability Testing |
|---|---|---|---|
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. | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 1-2 h je Session |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | Based on research question |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Usability Issues, Severity List, Recommendations |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | ValidationUXPrototype |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






