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 A3 Problem Solving |  Architecture Architecture Communication Canvas |  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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | 45-90 min | 60-120 min | 15-30 min |
Participantsdifferent | 4-10 | 2-5 | 2-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | A3 Report, Action Plan, Root Cause Analysis | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | LeanProblem solvingCoachingOperations | ArchitectureCommunicationStakeholdersCanvas | Root causeIncidentLeanProblem solving |