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 | ![]() Innovation Crazy 8s | ![]() Innovation Morphological 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. | With only a few minutes available and a still-fuzzy solution search, the method forces a wide range of variants. It produces fast sketches before the first idea can settle in, making different directions directly comparable and open to further development. | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-240 min | 8-15 min | 1-3 h |
Participantsdifferent | 1-6 | 1-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Sketch Set, Idea Shortlist, Direction Options | Morphological Box, Concept Combinations, Idea Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingSketchingSpeedDivergenceDesign sprint | IdeationInnovationCreativity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






