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 Reverse Brainstorming |  Innovation SCAMPER |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-240 min | 30-60 min | 30-60 min |
Participantsdifferent | 1-6 | 3-12 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Reverse Ideas, Risk Themes, Solution Ideas | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityRisk | BrainstormingIdeationCreativityReframingInnovation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
