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 |  Decision Making Assumption Surfacing |  Decision Making Decision Rights Mapping |
|---|---|---|---|---|
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. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 45-90 min | 90-180 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-8 | 4-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | Decision Rights Matrix, Agreement |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | DecisionGovernanceAlignmentResponsibility |