View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations Waste Analysis | ![]() Delivery RAID Log | ![]() Agile Ideal Days | ![]() Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-120 min | 30 min Setup, dann laufend | 15-60 min | 5-20 min |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 2-9 | 3-20 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | RAID Log, Status Report Source | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | WasteLeanProcess improvement | RiskTrackingStakeholdersGovernance | EstimationEffortAgile | EstimationEffortRisk |



