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 |  Product Strategy KPI Tree |  UX Research HEART Framework |
|---|---|---|---|---|
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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 1-3 Wochen | 90-180 min initial, dann laufend | 120 min initial, dann laufend |
Participantsdifferent | 2-8 | 4-12 Beobachtungen | 3-8 | 3-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Field Notes, Workflow Insights, Pain Points | KPI Tree, Owner List | HEART-GSM Table, Dashboard |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | UX researchObservationContext | MetricsStrategyAlignmentMeasurement | MetricsUX researchMeasurementSatisfaction |