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 | ![]() Innovation Design Thinking | ![]() Decision Making Decision Tree | ![]() Decision Making Pre-Mortem |
|---|---|---|---|---|
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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch. | 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 1-3 h | 1 Tag bis mehrere Wochen | 30-90 min | 20–45 min |
Participantsdifferent | 3-8 | 4-10 | 1-6 | Small cross-functional group |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Problem Statement, Prototype, Test Learnings | Decision Tree, Option Map, Assumption List | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | FailureResilienceRisk | InnovationPrototypeResearch | DecisionTreeOptions | RiskDecisionFailurePlanning |



