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 |  Facilitation Decision Jam |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-240 min | 20–45 min | 60-90 min | 45-90 min |
Participantsdifferent | 1-6 | Small cross-functional group | 4-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Risk list, Mitigation plan, Assumption log | Problem Cluster, Prioritized Challenge, Experiment | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | RiskDecisionFailurePlanning | FacilitationDecisionProblem solvingWorkshop | AssumptionsRiskDecisionDiscovery |