View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Pre-Mortem | ![]() Engineering Failure Scenario Analysis | ![]() Systems Thinking Evaporating Cloud | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20–45 min | 1-3 h | 60-120 min | 45-60 min |
Participantsdifferent | Small cross-functional group | 3-8 | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskDecisionFailurePlanning | FailureResilienceRisk | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskExperimentsValidation |



