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 |  Systems Thinking Evaporating Cloud |  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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | High |
Timedifferent | 1-3 h | 60-120 min | Half day |
Participantsdifferent | 2-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Value Chain Map, Lever List |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | Theory of ConstraintsAssumptionsSystems thinking | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
