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 Business Model Stress Test | ![]() Business Strategy VRIO Framework |
|---|---|---|---|---|
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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 1-2 h | 1-3 h | Half day | 90-180 min |
Participantsdifferent | 2-8 | 2-8 | 3-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain Story, Glossary Notes, Process Narrative | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario | VRIO Table, Strategic Actions |
Tagsno overlap | KnowledgeDomain-Driven DesignProcess | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis | StrategyDiagnosisBusiness modelCapability |



