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 |  Facilitation Decision Jam |  Operations A3 Problem Solving |
|---|---|---|---|---|
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 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Ongoing | 1-3 h | 60-90 min | 45-90 min |
Participantsdifferent | 2-12 | 4-10 | 4-10 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list | Problem Cluster, Prioritized Challenge, Experiment | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | FlowVisual managementDelivery | LeanFlowWasteDelivery | FacilitationDecisionProblem solvingWorkshop | LeanProblem solvingCoachingOperations |