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 Constraint Analysis |  Engineering Kanban |  Delivery Monte Carlo Forecasting |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 30-90 min | Ongoing | 30-90 min Setup, danach laufend | 45-90 min |
Participantsdifferent | 2-8 | 2-12 | 1-8 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Kanban board, WIP policies, Flow metrics | Forecast Percentiles, Throughput Dataset, Risk Communication | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | ConstraintsDecisionPlanningOptions | FlowVisual managementDelivery | ForecastingFlowDelivery | CommunicationStakeholdersDeliveryPlanning |