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 PERT Estimation |  Engineering Kanban |  Delivery RAID Log |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 15-45 min | Ongoing | 30 min Setup, dann laufend | 5-20 min |
Participantsdifferent | 1-8 | 2-12 | 1-3 maintaining, briefing for everyone | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | PERT Estimate, Expected Value, Risk Notes | Kanban board, WIP policies, Flow metrics | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | EstimationUncertaintyRisk | FlowVisual managementDelivery | RiskTrackingStakeholdersGovernance | EstimationEffortRisk |