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 |  Engineering Kanban |  Decision Making Pre-Mortem |  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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-3 h | Ongoing | 20–45 min | 45-90 min |
Participantsdifferent | 3-8 | 2-12 | Small cross-functional group | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Kanban board, WIP policies, Flow metrics | Risk list, Mitigation plan, Assumption log | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | FailureResilienceRisk | FlowVisual managementDelivery | RiskDecisionFailurePlanning | CommunicationStakeholdersDeliveryPlanning |