View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Delivery Value Stream Mapping |  Decision Making Decision Framing Workshop |
|---|---|---|---|
Purposedifferent | 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. | 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 a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Ongoing | 1-3 h | 60-120 min |
Participantsdifferent | 2-12 | 4-10 | 4-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Decision Frame, Decision Question, Criteria List, Evidence Plan |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | Decision framingAlignmentCriteriaOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
