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 RAID Log |  DevOps Blameless Postmortem |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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 | Low | Medium | High |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 30-90 min | Halber Tag |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 3-12 | 5-20 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Postmortem Doc, Action Items, Timeline | Simulation Notes, Gaps List, Updated Runbooks |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | Site Reliability EngineeringIncidentLearningReliability | ResilienceOperationsIncident |