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 HEART Framework | ![]() UX Research Contextual Inquiry |
|---|---|---|---|
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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-3 h | 120 min initial, dann laufend | 1-3 Wochen |
Participantsdifferent | 3-10 | 3-6 | 4-12 Beobachtungen |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | HEART-GSM Table, Dashboard | Field Notes, Workflow Insights, Pain Points |
Tagsno overlap | Domain-Driven DesignContextBoundaries | MetricsUX researchMeasurementSatisfaction | UX researchObservationContext |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






