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 PDCA Cycle |  Operations 5 Whys |  Operations Barrier Analysis |
|---|---|---|---|---|
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. | For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 1 h bis mehrere Wochen | 15-30 min | 2-4 h |
Participantsdifferent | 4-10 | 1-8 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | PDCA Log, Experiment Plan, Learning Outcome, Standard Change | Root cause notes, Countermeasures | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | LeanFlowWasteDelivery | Continuous improvementLeanExperiments | Root causeIncidentLeanProblem solving | Root causeSafetyIncident |