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 |  Product Strategy RICE Scoring |  Delivery Cost of Delay |  Engineering Kanban |
|---|---|---|---|---|
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 many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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 | High | Medium |
Timedifferent | 1-3 h | 60-90 min | 90-180 min | Ongoing |
Participantsdifferent | 4-10 | 2-10 | 3-8 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RICE Scores, Ranked List, Assumption Log | CoD Table, Prioritization Sequence | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | PrioritizationScoringRoadmapTradeoffs | PrioritizationDeliveryEconomicsDecision | FlowVisual managementDelivery |