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 |  Engineering Kanban |  Decision Making Delphi Method |  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 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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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 | High | Medium |
Timedifferent | 1-3 h | Ongoing | 1-4 Wochen | 1-3 h |
Participantsdifferent | 2-8 | 2-12 | 6-30 Experten | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Kanban board, WIP policies, Flow metrics | Expert Forecast, Consensus Range, Assumption Notes | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | FlowVisual managementDelivery | ForecastingExpertsDecisionStrategy | Domain-Driven DesignBoundariesModeling |