View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Constraint Analysis |  Operations Change Analysis |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|
Purposedifferent | 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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 30-90 min | 45-120 min | 30-240 min |
Participantsdifferent | 2-8 | 2-6 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ChangeRoot causeTroubleshootingComparison | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
