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 | ![]() Agile 4Ls Retrospective | ![]() Decision Making Pre-Mortem | ![]() Decision Making Constraint Analysis |
|---|---|---|---|---|
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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 45–75 min | 20–45 min | 30-90 min |
Participantsdifferent | 3-8 | Team members involved | Small cross-functional group | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | 4Ls Board, Learning Themes, Improvement Actions | Risk list, Mitigation plan, Assumption log | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | FailureResilienceRisk | RetrospectiveLearningReflectionTeam | RiskDecisionFailurePlanning | ConstraintsDecisionPlanningOptions |



