View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Three-Point Estimation |  Engineering Kanban |  Decision Making OODA Loop |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 10-30 min je Item | Ongoing | 15-60 min je Zyklus | 30-90 min Setup, danach laufend |
Participantsdifferent | 1-8 | 2-12 | 1-8 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Kanban board, WIP policies, Flow metrics | Situation Assessment, Decision Loop, Action Updates | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | EstimationUncertaintyForecasting | FlowVisual managementDelivery | DecisionChangeLearningStrategy | ForecastingFlowDelivery |