View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Waste Analysis |  Delivery Value Stream Mapping |  Delivery RAID Log |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium | Low | Medium |
Timedifferent | 45-120 min | 1-3 h | 30 min Setup, dann laufend | Ongoing |
Participantsdifferent | 2-8 | 4-10 | 1-3 maintaining, briefing for everyone | 2-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Waste Map, Prioritized Waste, Improvement Backlog | Current-state map, Future-state map, Bottleneck list | RAID Log, Status Report Source | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | WasteLeanProcess improvement | LeanFlowWasteDelivery | RiskTrackingStakeholdersGovernance | FlowVisual managementDelivery |