View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Domain Modeling Bounded Context Canvas |  Business Strategy Value Chain Analysis |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 60-120 min | 1-3 h | Half day | 1-3 h |
Participantsdifferent | 2-8 | 3-8 | 3-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Context Canvas, Glossary, Integration Notes | Value Chain Map, Lever List | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | Domain-Driven DesignBoundariesModeling | StrategyBusiness modelDiagnosisAnalysis | Domain-Driven DesignBoundariesStrategy |