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 |  Engineering Kanban |  Business Strategy PESTLE Analysis |  Business Strategy GAP Analysis |
|---|---|---|---|---|
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. | 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. | PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | 30-90 min Setup, danach laufend | Ongoing | 1-3 h | 1-3 h |
Participantsdifferent | 1-8 | 2-12 | 2-10 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics | PESTLE Map, External Risks, Strategic Questions | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | ForecastingFlowDelivery | FlowVisual managementDelivery | StrategyMarketAnalysis | StrategyAnalysisPlanning |