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 | ![]() Engineering Failure Scenario Analysis | ![]() Operations Root Cause Analysis |
|---|---|---|---|
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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 60-120 min | 1-3 h | 1-4 h |
Participantsdifferent | 2-8 | 3-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ContradictionsInnovationProblem solving | FailureResilienceRisk | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






