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 |  Business Strategy Balanced Scorecard |  Engineering Goal Question Metric |  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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | 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 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 | High | Medium | Medium |
Timedifferent | 1-2 h | Halber Tag bis mehrere Wochen | 90-180 min | 1-3 h |
Participantsdifferent | 2-8 | 4-12 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Balanced Scorecard, Strategic Measures, Initiative Map | GQM Table, Metric Profiles | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | StrategyMetricsExecution | MetricsMeasurementEngineeringAlignment | Domain-Driven DesignBoundariesStrategy |