View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Architecture Risk Storming |  Operations A3 Problem Solving |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Halber Tag | 60-90 min | 45-90 min | 45-60 min |
Participantsdifferent | 5-20 | 4-12 | 2-5 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Annotated Diagram, Prioritized Risk List, Action Backlog | A3 Report, Action Plan, Root Cause Analysis | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | ResilienceOperationsIncident | RiskArchitectureWorkshopValidation | LeanProblem solvingCoachingOperations | AssumptionsRiskExperimentsValidation |