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 Morphological Analysis |  Engineering Fault Isolation |  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. | 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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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 | Medium | Medium | Low |
Timedifferent | 30-240 min | 1-3 h | 30-180 min | 30-60 min |
Participantsdifferent | 1-6 | 2-8 | 1-6 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Morphological Box, Concept Combinations, Idea Shortlist | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | IdeationInnovationCreativity | TroubleshootingDiagnosisEngineering | BrainstormingIdeationCreativityReframingInnovation |