View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Evaporating Cloud |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|
Purposedifferent | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitysame | Medium | Medium |
Timedifferent | 60-120 min | 30-240 min |
Participantsdifferent | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop + async |
Outputdifferent | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | Theory of ConstraintsAssumptionsSystems thinking | TroubleshootingProblem solvingDiagnosis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
