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 5 Whys |  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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Medium | Low | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 15-30 min | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 2-6 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Context Map, Integration Patterns, Boundary Notes | Root cause notes, Countermeasures | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignBoundariesStrategy | Root causeIncidentLeanProblem solving | Domain-Driven DesignContextBoundaries |