View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Facilitation Dot Estimation | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | 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 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-3 h | 5-20 min | 45-60 min |
Participantsdifferent | 4-10 | 3-20 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Effort Heatmap, Risk Signals, Discussion Targets | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | LeanFlowWasteDelivery | EstimationEffortRisk | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






