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 | ![]() Operations Time Blocking | ![]() 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. | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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 | Low | Medium |
Timedifferent | 1-3 h | 15-30 min Planung, laufend | Ongoing |
Participantsdifferent | 4-10 | 1 | 2-12 |
Formatdifferent | Workshop | Async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Blocked Calendar, Capacity View, Focus Plan | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | PlanningTime managementFocus | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






