View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  UX Research Contextual Inquiry |  Facilitation Stakeholder Mapping |  Domain Modeling Domain Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 h | 1-3 Wochen | 60–90 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 Beobachtungen | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Field Notes, Workflow Insights, Pain Points | Stakeholder Map, Engagement Plan, Risk Notes | Domain Context Map, Boundary Notes, Ownership Map |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | UX researchObservationContext | StakeholdersAlignmentFacilitationChange | Domain-Driven DesignContextBoundaries |