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 |  Decision Making Pre-Mortem |  Product Discovery Problem Interview |  Product Discovery Assumption 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. | 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 the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 20–45 min | 30-60 min je Interview | 45-60 min |
Participantsdifferent | 3-8 | Small cross-functional group | 5-12 Interviews | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Risk list, Mitigation plan, Assumption log | Problem Evidence, Risk Notes, Customer Segments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | FailureResilienceRisk | RiskDecisionFailurePlanning | DiscoveryInterviewsValidation | AssumptionsRiskExperimentsValidation |