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 Constraint Analysis |  Delivery Communication Plan |
|---|---|---|---|---|
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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 30-90 min | 45-90 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-8 | 2-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | ConstraintsDecisionPlanningOptions | CommunicationStakeholdersDeliveryPlanning |