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 Value Stream Mapping |  Systems Thinking Leverage Points |  Domain Modeling Context Map |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | Half day | 1-3 h | 1-3 h |
Participantsdifferent | 4-10 | 3-12 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Leverage Map, Action Strategy | Context Map, Integration Patterns, Boundary Notes | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | LeanFlowWasteDelivery | Systems thinkingChangeStrategy | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignBoundariesModeling |