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 A3 Problem Solving |  Delivery Value Stream Mapping |  Architecture Architecture Decision Record |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 15-45 min | 15-30 min |
Participantsdifferent | 2-5 | 4-10 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Current-state map, Future-state map, Bottleneck list | ADR File, Decision Log, Rationale | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | LeanFlowWasteDelivery | ArchitectureRationaleDocumentationGovernance | Root causeIncidentLeanProblem solving |