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 |  Business Strategy VRIO Framework |  Agile Ideal Days |
|---|---|---|---|---|
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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 5-20 min | 90-180 min | 15-60 min |
Participantsdifferent | 4-10 | 3-20 | 3-6 | 2-9 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Effort Heatmap, Risk Signals, Discussion Targets | VRIO Table, Strategic Actions | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | LeanFlowWasteDelivery | EstimationEffortRisk | StrategyDiagnosisBusiness modelCapability | EstimationEffortAgile |