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 |  Systems Thinking Evaporating Cloud |  Decision Making Delphi Method |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | Ongoing | 60-120 min | 1-4 Wochen | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 2-8 | 6-30 Experten | 1-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Expert Forecast, Consensus Range, Assumption Notes | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | Theory of ConstraintsAssumptionsSystems thinking | ForecastingExpertsDecisionStrategy | ForecastingFlowDelivery |