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 Kepner-Tregoe |  Facilitation Consensus Workshop |  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. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 | High | Medium | Low |
Timedifferent | 1-3 h | 2-8 h | 1-3 h | 15-30 min |
Participantsdifferent | 4-10 | 2-8 | 5-30 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Problem Analysis, Decision Analysis, Risk Plan | Consensus Clusters, Theme Titles, Priority Areas | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | Problem solvingRoot causeDecisionOperations | FacilitationConsensusWorkshopAlignment | Root causeIncidentLeanProblem solving |