View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations After-Action Review | ![]() Innovation Contradiction Analysis | ![]() Operations Kepner-Tregoe | ![]() Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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. | 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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 20-45 min | 60-120 min | 2-8 h | 15-30 min |
Participantsdifferent | 3-12 | 2-8 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Lessons learned, Action items, Event summary | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Problem Analysis, Decision Analysis, Risk Plan | Root cause notes, Countermeasures |
Tagsno overlap | LearningOperationsImprovement | ContradictionsInnovationProblem solving | Problem solvingRoot causeDecisionOperations | Root causeIncidentLeanProblem solving |



