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 |  Decision Making Assumption Surfacing |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Risk Storming |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Halber Tag | 45-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min |
Participantsdifferent | 5-20 | 2-8 | Designers, developers as users, and facilitation | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Assumption List, Critical Assumptions, Learning Plan | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ResilienceOperationsIncident | AssumptionsRiskDecisionDiscovery | ArchitectureEngineeringFeedbackValidationTasks | RiskArchitectureWorkshopValidation |