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 SCAMPER |  Innovation Crazy 8s |
|---|---|---|---|
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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-240 min | 30-60 min | 8-15 min |
Participantsdifferent | 1-6 | 2-10 | 1-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | SCAMPER Idea List, Concept Shortlist, Variation Notes | Sketch Set, Idea Shortlist, Direction Options |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityReframingInnovation | BrainstormingSketchingSpeedDivergenceDesign sprint |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
