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 Fault Isolation |  Decision Making Constraint Analysis |  Engineering Hypothesis-Driven Troubleshooting |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-180 min | 30-90 min | 30-240 min | 20–45 min |
Participantsdifferent | 1-6 | 2-8 | 1-6 | Small cross-functional group |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ConstraintsDecisionPlanningOptions | TroubleshootingProblem solvingDiagnosis | RiskDecisionFailurePlanning |