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 | ![]() Decision Making Pre-Mortem | ![]() Delivery RAID Log |
|---|---|---|---|
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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 20–45 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | Small cross-functional group | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Risk list, Mitigation plan, Assumption log | RAID Log, Status Report Source |
Tags1 shared | FailureResilienceRisk | RiskDecisionFailurePlanning | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






