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 8D Problem Solving |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-3 Wochen | 1-3 h | 1-6 Wochen | 1-3 h |
Participantsdifferent | 4-12 Beobachtungen | 2-8 | 4-10 | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Field Notes, Workflow Insights, Pain Points | Context Map, Integration Patterns, Boundary Notes | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | UX researchObservationContext | Domain-Driven DesignBoundariesStrategy | QualityProblem solvingRoot cause | Domain-Driven DesignBoundariesModeling |