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 |  Systems Thinking Iceberg Model |  Operations Bottleneck Analysis |  Operations 5 Whys |
|---|---|---|---|---|
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. | The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 30-60 min | 1-3 h | 15-30 min |
Participantsdifferent | 4-10 | 2-10 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | Systems thinkingRoot causePatterns | FlowMeasurementConstraints | Root causeIncidentLeanProblem solving |