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 |  Product Discovery Dual-Track Agile |  Facilitation Dot Estimation |  Engineering Kanban |
|---|---|---|---|---|
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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | Laufend, Wochen bis Monate | 5-20 min | Ongoing |
Participantsdifferent | 3-8 | 4-10 | 3-20 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Effort Heatmap, Risk Signals, Discussion Targets | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | FlowMeasurementConstraints | AgileDiscoveryDelivery | EstimationEffortRisk | FlowVisual managementDelivery |