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 Reverse Brainstorming |  Innovation Brainstorming |
|---|---|---|---|---|
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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. | 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 | Medium | Low | Low | Low |
Timedifferent | 30-240 min | 30-60 min | 30-60 min | 30-60 min |
Participantsdifferent | 1-6 | 2-10 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | SCAMPER Idea List, Concept Shortlist, Variation Notes | Reverse Ideas, Risk Themes, Solution Ideas | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityWorkshopDivergence |