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 |  Knowledge Modeling Domain Storytelling |  Product Strategy KPI Tree |  Engineering Goal Question Metric |
|---|---|---|---|---|
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. | Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected. | 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 technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 1-2 h | 90-180 min initial, dann laufend | 90-180 min |
Participantsdifferent | 2-8 | 2-8 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain Story, Glossary Notes, Process Narrative | KPI Tree, Owner List | GQM Table, Metric Profiles |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | KnowledgeDomain-Driven DesignProcess | MetricsStrategyAlignmentMeasurement | MetricsMeasurementEngineeringAlignment |