View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Domain Storytelling |  Engineering Goal Question Metric |  Product Strategy KPI Tree |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1-2 h | 90-180 min | 90-180 min initial, dann laufend | 1-3 h |
Participantsdifferent | 2-8 | 3-6 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | GQM Table, Metric Profiles | KPI Tree, Owner List | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | MetricsMeasurementEngineeringAlignment | MetricsStrategyAlignmentMeasurement | Domain-Driven DesignBoundariesStrategy |