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 |  UX Research Contextual Inquiry |  Operations A3 Problem Solving |  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. | When work processes are known only from accounts and the real context stays hidden, Contextual Inquiry makes behavior at the workplace visible. Observation and follow-up questions together show how people actually work, get interrupted, and improvise. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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 | Medium | Medium | Low |
Timedifferent | 1-3 h | 1-3 Wochen | 45-90 min | 15-30 min |
Participantsdifferent | 4-10 | 4-12 Beobachtungen | 2-5 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Field Notes, Workflow Insights, Pain Points | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | UX researchObservationContext | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving |