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 Architecture Decision Record |  Operations 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 1-3 h | 15-45 min | 15-30 min | 1-6 Wochen |
Participantsdifferent | 4-10 | 1-3 | 2-6 | 4-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |