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 Rapid Ideation |  Innovation Crazy 8s |  Innovation Lotus Blossom |
|---|---|---|---|---|
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 decision needs to be prepared quickly, the method generates many solution-close variants in a short time. It deliberately relies on pace to undercut self-censorship and perfectionism. This quickly produces a usable field for prioritization and further work. | With only a few minutes available and a still-fuzzy solution search, the method forces a wide range of variants. It produces fast sketches before the first idea can settle in, making different directions directly comparable and open to further development. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 30-240 min | 5-20 min | 8-15 min | 45-90 min |
Participantsdifferent | 1-6 | 1-20 | 1-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Ideenpool, Roh-Shortlist, Cluster | Sketch Set, Idea Shortlist, Direction Options | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationDivergenceSpeed | BrainstormingSketchingSpeedDivergenceDesign sprint | BrainstormingIdeationCreativityDivergenceWorkshop |