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 Bottleneck Analysis |  Engineering Kanban |  Facilitation Dot Estimation |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. | 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | Ongoing | 5-20 min | laufend |
Participantsdifferent | 3-8 | 2-12 | 3-20 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Kanban board, WIP policies, Flow metrics | Effort Heatmap, Risk Signals, Discussion Targets | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | FlowMeasurementConstraints | FlowVisual managementDelivery | EstimationEffortRisk | EstimationForecastingFlow |