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 |  Architecture Architecture Decision Record |  Decision Making Pre-Mortem |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 15-45 min | 20–45 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 1-3 | Small cross-functional group |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | RiskDecisionFailurePlanning |