View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Business Strategy Business Model Stress Test |  Knowledge Modeling Knowledge Mapping |  Business Strategy Value Chain Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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 | Medium | High | Medium | High |
Timedifferent | 1-3 h | Half day | 1-3 h | Half day |
Participantsdifferent | 2-8 | 3-8 | 3-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Value Chain Map, Lever List |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis | KnowledgeMappingRisk | StrategyBusiness modelDiagnosisAnalysis |