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 | ![]() Facilitation Dot Estimation | ![]() Operations A3 Problem Solving | ![]() Agile Ideal Days |
|---|---|---|---|---|
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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-120 min | 5-20 min | 45-90 min | 15-60 min |
Participantsdifferent | 2-8 | 3-20 | 2-5 | 2-9 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Effort Heatmap, Risk Signals, Discussion Targets | A3 Report, Action Plan, Root Cause Analysis | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | WasteLeanProcess improvement | EstimationEffortRisk | LeanProblem solvingCoachingOperations | EstimationEffortAgile |



