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 Domain Context Map |  Operations Waste Analysis |  Engineering Kanban |  Delivery Value Stream Mapping |
|---|---|---|---|---|
Purposedifferent | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 45-120 min | Ongoing | 1-3 h |
Participantsdifferent | 3-10 | 2-8 | 2-12 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Waste Map, Prioritized Waste, Improvement Backlog | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | Domain-Driven DesignContextBoundaries | WasteLeanProcess improvement | FlowVisual managementDelivery | LeanFlowWasteDelivery |