View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Operations Bottleneck Analysis |  Domain Modeling Bounded Context Canvas |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Ongoing | 1-3 h | 1-3 h | 1-3 h |
Participantsdifferent | 2-12 | 3-8 | 3-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Context Canvas, Glossary, Integration Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | FlowVisual managementDelivery | FlowMeasurementConstraints | Domain-Driven DesignBoundariesModeling | Domain-Driven DesignBoundariesStrategy |