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 Round Robin Brainstorming |  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. | With unevenly distributed speaking time, the method brings every person into the contribution one after another. It prevents early voices from setting the direction while still producing a shared idea space. This makes participation plannable and the team's diversity visible. | 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 |
Timedifferent | 30-240 min | 20-45 min | 45-90 min |
Participantsdifferent | 1-6 | 4-10 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Idea List, Cluster, Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationFacilitationInclusionCreativity | BrainstormingIdeationCreativityDivergenceWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
