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 |  Product Strategy KPI Tree |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 120 min initial, dann laufend | 90-180 min initial, dann laufend | 1-2 h |
Participantsdifferent | 3-10 | 3-6 | 3-8 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | HEART-GSM Table, Dashboard | KPI Tree, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Domain-Driven DesignContextBoundaries | MetricsUX researchMeasurementSatisfaction | MetricsStrategyAlignmentMeasurement | AlignmentStakeholdersStrategyFacilitation |