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 Lotus Blossom |  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. | When a central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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 | 45-90 min | 30-60 min |
Participantsdifferent | 1-6 | 3-10 | 2-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Lotus Diagram, Idea Themes, Shortlist | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityDivergenceWorkshop | BrainstormingIdeationCreativityReframingInnovation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
