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 8D Problem Solving |  Delivery Value Stream Mapping |  Architecture Architecture Communication Canvas |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 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 | High | Medium | Medium | Low |
Timedifferent | 1-6 Wochen | 1-3 h | 60-120 min | 15-30 min |
Participantsdifferent | 4-10 | 4-10 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Current-state map, Future-state map, Bottleneck list | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Root cause notes, Countermeasures |
Tagsno overlap | QualityProblem solvingRoot cause | LeanFlowWasteDelivery | ArchitectureCommunicationStakeholdersCanvas | Root causeIncidentLeanProblem solving |