View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation SCAMPER |  Engineering Hypothesis-Driven Troubleshooting |  Innovation Brainstorming |
|---|---|---|---|
Purposedifferent | 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. | 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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30-60 min | 30-240 min | 30-60 min |
Participantsdifferent | 2-10 | 1-6 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | SCAMPER Idea List, Concept Shortlist, Variation Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | BrainstormingIdeationCreativityReframingInnovation | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityWorkshopDivergence |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
