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 |  Delivery Monte Carlo Forecasting |  Systems Thinking Leverage Points |  Decision Making Force Field Analysis |
|---|---|---|---|---|
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. | 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. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | Ongoing | 30-90 min Setup, danach laufend | Half day | 45-90 min |
Participantsdifferent | 2-12 | 1-8 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Leverage Map, Action Strategy | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | FlowVisual managementDelivery | ForecastingFlowDelivery | Systems thinkingChangeStrategy | ChangeDecisionStrategy |