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 Waste Analysis |  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. | 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 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 | Low | High | Low |
Timedifferent | Ongoing | 45-120 min | 1-4 Wochen | 1-2 h |
Participantsdifferent | 2-12 | 2-8 | 6-30 Experten | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Waste Map, Prioritized Waste, Improvement Backlog | Expert Forecast, Consensus Range, Assumption Notes | DIBB document, Belief list, Bet list, Learning report |
Tagsno overlap | FlowVisual managementDelivery | WasteLeanProcess improvement | ForecastingExpertsDecisionStrategy | StrategyDecisionAssumptionsHypothesis |