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 | ![]() Agile Ideal Days | ![]() Delivery Value Stream Mapping | ![]() Product Discovery Dual-Track Agile |
|---|---|---|---|---|
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 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 delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-120 min | 15-60 min | 1-3 h | Laufend, Wochen bis Monate |
Participantsdifferent | 2-8 | 2-9 | 4-10 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Current-state map, Future-state map, Bottleneck list | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | WasteLeanProcess improvement | EstimationEffortAgile | LeanFlowWasteDelivery | AgileDiscoveryDelivery |



