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 Time Blocking |  Delivery Value Stream Mapping |  Operations 5 Whys |  Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-30 min Planung, laufend | 1-3 h | 15-30 min | 1-4 h |
Participantsdifferent | 1 | 4-10 | 2-6 | 3-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | Current-state map, Future-state map, Bottleneck list | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | PlanningTime managementFocus | LeanFlowWasteDelivery | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |