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 |  Domain Modeling Context Map |  Decision Making Delphi Method |  Product Strategy DIBB |
|---|---|---|---|---|
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. | 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 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. | DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | Ongoing | 1-3 h | 1-4 Wochen | 1-2 h |
Participantsdifferent | 2-12 | 2-8 | 6-30 Experten | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | FlowVisual managementDelivery | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy | StrategyDecisionAssumptionsHypothesis |