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 Brainstorming |  Innovation Morphological Analysis |  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 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. | For a search for solutions with many degrees of freedom, a grid emerges for systematic combinations. The method separates features, variants, and exclusion criteria, so the space gets explored deliberately. | 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 | Medium | Low |
Timedifferent | 30-240 min | 30-60 min | 1-3 h | 45-90 min |
Participantsdifferent | 1-6 | 4-12 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Idea pool, Theme clusters, Shortlist | Morphological Box, Concept Combinations, Idea Shortlist | Lotus Diagram, Idea Themes, Shortlist |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | BrainstormingIdeationCreativityWorkshopDivergence | IdeationInnovationCreativity | BrainstormingIdeationCreativityDivergenceWorkshop |