View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Domain Modeling Context Map | ![]() Business Strategy Business Model Stress Test | ![]() Business Strategy Value Chain Analysis |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | High |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | Half day | Half day |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario | Value Chain Map, Lever List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis | StrategyBusiness modelDiagnosisAnalysis |



