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 TRIZ |  Engineering Hypothesis-Driven Troubleshooting |  Innovation SCAMPER |  Innovation Brainstorming |
|---|---|---|---|---|
Purposedifferent | For technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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. | 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 | High | Medium | Low | Low |
Timedifferent | 1-4 h | 30-240 min | 30-60 min | 30-60 min |
Participantsdifferent | 2-8 | 1-6 | 2-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | SCAMPER Idea List, Concept Shortlist, Variation Notes | Idea pool, Theme clusters, Shortlist |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityReframingInnovation | BrainstormingIdeationCreativityWorkshopDivergence |