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 Barrier Analysis |
|---|---|---|---|
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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 2-4 h |
Participantsdifferent | 4-12 Beobachtungen | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Domain Context Map, Boundary Notes, Ownership Map | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignContextBoundaries | Root causeSafetyIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






