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 | ![]() Decision Making Force Field Analysis | ![]() Engineering Kanban | ![]() Delivery Cost of Delay |
|---|---|---|---|---|
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. | 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. | 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, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | High | Low | Medium | High |
Timedifferent | 30-90 min Setup, danach laufend | 45-90 min | Ongoing | 90-180 min |
Participantsdifferent | 1-8 | 3-12 | 2-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Force Field Map, Change Levers, Risk Notes | Kanban board, WIP policies, Flow metrics | CoD Table, Prioritization Sequence |
Tagsno overlap | ForecastingFlowDelivery | ChangeDecisionStrategy | FlowVisual managementDelivery | PrioritizationDeliveryEconomicsDecision |



