View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation Contradiction Analysis | ![]() Operations Change Analysis | ![]() Innovation TRIZ | ![]() Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|---|
Purposedifferent | When a system should improve while another measure suffers as a result, the method makes the underlying conflict precisely formulable. It separates the desired effect from its side effect. This makes solutions possible that address the contradiction deliberately instead of half-heartedly. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. | 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 | Medium | High | Medium |
Timedifferent | 60-120 min | 45-120 min | 1-4 h | 30-240 min |
Participantsdifferent | 2-8 | 2-6 | 2-8 | 1-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Contradiction Statement, Inventive Principles, Solution Concepts | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | ContradictionsInnovationProblem solving | ChangeRoot causeTroubleshootingComparison | InnovationProblem solvingContradictionsCreativity | TroubleshootingProblem solvingDiagnosis |



