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 |  Delivery Value Stream Mapping |  Operations Waste Analysis |  Domain Modeling Bounded Context Canvas |
|---|---|---|---|---|
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. | 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. | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 45-120 min | 1-3 h |
Participantsdifferent | 2-8 | 4-10 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Current-state map, Future-state map, Bottleneck list | Waste Map, Prioritized Waste, Improvement Backlog | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | LeanFlowWasteDelivery | WasteLeanProcess improvement | Domain-Driven DesignBoundariesModeling |