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 Domain Context Map | ![]() UX Research Contextual Inquiry | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | 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. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen | 60-90 min |
Participantsdifferent | 3-10 | 4-12 Beobachtungen | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Field Notes, Workflow Insights, Pain Points | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignContextBoundaries | UX researchObservationContext | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






