View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Monte Carlo Forecasting |  Systems Thinking Evaporating Cloud |  Systems Thinking Intervention Mapping |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. |
Complexitydifferent | High | Medium | High | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 60-120 min | 1-5 Tage | Ongoing |
Participantsdifferent | 1-8 | 2-8 | 4-12 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ForecastingFlowDelivery | Theory of ConstraintsAssumptionsSystems thinking | ChangeSystems thinkingCapability | FlowVisual managementDelivery |