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 Red Teaming |  Decision Making Cynefin Workshop |
|---|---|---|---|---|
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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-4 h | 60-180 min |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 3-8 | 4-20 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | RAID Log, Status Report Source | Challenge Findings, Risk Register, Mitigation Plan | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | FailureResilienceRisk | RiskTrackingStakeholdersGovernance | RiskDecisionSensemaking | ComplexitySensemakingDecision |