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 Fault Isolation |  Innovation TRIZ |  Innovation SCAMPER |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|---|
Purposedifferent | 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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 30-180 min | 1-4 h | 30-60 min | 30-240 min |
Participantsdifferent | 1-6 | 2-8 | 2-10 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Contradiction Statement, Inventive Principles, Solution Concepts | SCAMPER Idea List, Concept Shortlist, Variation Notes | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | TroubleshootingDiagnosisEngineering | InnovationProblem solvingContradictionsCreativity | BrainstormingIdeationCreativityReframingInnovation | TroubleshootingProblem solvingDiagnosis |