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 Hypothesis-Driven Troubleshooting |  Decision Making Pre-Mortem |  Decision Making Constraint Analysis |
|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 |
Timedifferent | 30-240 min | 20–45 min | 30-90 min |
Participantsdifferent | 1-6 | Small cross-functional group | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Risk list, Mitigation plan, Assumption log | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | RiskDecisionFailurePlanning | ConstraintsDecisionPlanningOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
