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 |  Innovation TRIZ |  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. | 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. | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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 | High | High | Low |
Timedifferent | 45-90 min | Halber Tag | 1-4 h | 15-30 min |
Participantsdifferent | 2-5 | 5-20 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Simulation Notes, Gaps List, Updated Runbooks | Contradiction Statement, Inventive Principles, Solution Concepts | Root cause notes, Countermeasures |
Tagsno overlap | LeanProblem solvingCoachingOperations | ResilienceOperationsIncident | InnovationProblem solvingContradictionsCreativity | Root causeIncidentLeanProblem solving |