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 RAID Log | ![]() Facilitation Dot Estimation | ![]() Delivery Communication Plan | ![]() Decision Making PERT Estimation |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 5-20 min | 45-90 min | 15-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-20 | 2-6 | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets | Communication Plan, Channel Matrix, Message Cadence | PERT Estimate, Expected Value, Risk Notes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | EstimationEffortRisk | CommunicationStakeholdersDeliveryPlanning | EstimationUncertaintyRisk |



