View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Delivery Monte Carlo Forecasting |  Engineering Kanban |  Systems Thinking Theory of Constraints Thinking Process |
|---|---|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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 Theory of Constraints Thinking Process exposes a system's bottleneck and the logic behind it. It suits situations where many symptoms trace back to the same limiting relationship. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 60-120 min | 30-90 min Setup, danach laufend | Ongoing | 0.5-3 Tage |
Participantsdifferent | 2-8 | 1-8 | 2-12 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics | Current Reality Logic, Conflict Cloud, Future Reality Tree, Implementation Obstacles |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ForecastingFlowDelivery | FlowVisual managementDelivery | Theory of ConstraintsConstraintsSystems thinkingCausality |