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 |  Product Strategy Lean Canvas |  Engineering Kanban |
|---|---|---|---|---|
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 an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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 | Medium | High | Medium | Medium |
Timedifferent | 60-120 min | 30-90 min Setup, danach laufend | 45-90 min | Ongoing |
Participantsdifferent | 2-8 | 1-8 | 1-6 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Forecast Percentiles, Throughput Dataset, Risk Communication | Lean Canvas, Core Assumptions, Experiment Backlog | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | ForecastingFlowDelivery | StartupLeanAssumptionsBusiness model | FlowVisual managementDelivery |