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 | ![]() Business Strategy Value Chain Analysis |
|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 1-2 h | 1-3 h | Half day |
Participantsdifferent | 2-8 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | Value Chain Map, Lever List |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






