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 | ![]() Domain Modeling Context Map | ![]() Operations Weekly Review | ![]() Business Strategy Balanced Scorecard |
|---|---|---|---|---|
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. | 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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 1-2 h | 1-3 h | 30-60 min | Halber Tag bis mehrere Wochen |
Participantsdifferent | 2-8 | 2-8 | 1 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | Updated Task System, Weekly Focus, Next Actions | Balanced Scorecard, Strategic Measures, Initiative Map |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | ProductivityExecutionPlanning | StrategyMetricsExecution |



