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 |  Architecture C4 Model |  Operations 8D 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 | Low | High | Low |
Timedifferent | 1-3 h | 1-4 h | 1-6 Wochen | 15-30 min |
Participantsdifferent | 4-10 | 1-5 | 4-10 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Context Diagram, Container Diagram, Component Diagram | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Root cause notes, Countermeasures |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureCommunicationVisualization | QualityProblem solvingRoot cause | Root causeIncidentLeanProblem solving |