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 After-Action Review |  Operations 5 Whys |  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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-120 min | 20-45 min | 15-30 min | 1-4 h |
Participantsdifferent | 2-8 | 3-12 | 2-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Lessons learned, Action items, Event summary | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | ContradictionsInnovationProblem solving | LearningOperationsImprovement | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |