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 Context Map |  Operations Barrier Analysis |  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. | 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. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 2-4 h | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 2-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Context Map, Integration Patterns, Boundary Notes | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignBoundariesStrategy | Root causeSafetyIncident | Domain-Driven DesignContextBoundaries |