View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Delivery Value Stream Mapping |  Operations Gemba Walk |  DevOps Game Day |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 h | 1-3 h | 30-120 min | Halber Tag |
Participantsdifferent | 3-8 | 4-10 | 2-6 | 5-20 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Current-state map, Future-state map, Bottleneck list | Observation Notes, Improvement Ideas | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FailureResilienceRisk | LeanFlowWasteDelivery | LeanObservationProcessOperations | ResilienceOperationsIncident |