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 | ![]() DevOps Game Day | ![]() Delivery Value Stream Mapping | ![]() Operations Gemba Walk |
|---|---|---|---|---|
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. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 45-90 min | Halber Tag | 1-3 h | 30-120 min |
Participantsdifferent | 2-5 | 5-20 | 4-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Simulation Notes, Gaps List, Updated Runbooks | Current-state map, Future-state map, Bottleneck list | Observation Notes, Improvement Ideas |
Tagsno overlap | LeanProblem solvingCoachingOperations | ResilienceOperationsIncident | LeanFlowWasteDelivery | LeanObservationProcessOperations |



