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 | ![]() Engineering Kanban | ![]() Facilitation Decision Jam |
|---|---|---|---|
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 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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | Ongoing | 60-90 min |
Participantsdifferent | 4-10 | 2-12 | 4-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Problem Cluster, Prioritized Challenge, Experiment |
Tagsno overlap | LeanFlowWasteDelivery | FlowVisual managementDelivery | FacilitationDecisionProblem solvingWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






