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 |  Facilitation Decision Jam |  Business Strategy Value Chain 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. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 30-240 min | 60-90 min | Half day |
Participantsdifferent | 1-6 | 4-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Problem Cluster, Prioritized Challenge, Experiment | Value Chain Map, Lever List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | FacilitationDecisionProblem solvingWorkshop | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
