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 |  Agile Sprint Retrospective |  Innovation TRIZ |  Operations After-Action Review |
|---|---|---|---|---|
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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 60-120 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-4 h | 20-45 min |
Participantsdifferent | 2-8 | Scrum Team | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Improvement actions, Team agreements | Contradiction Statement, Inventive Principles, Solution Concepts | Lessons learned, Action items, Event summary |
Tagsno overlap | ContradictionsInnovationProblem solving | RetrospectiveImprovementLearning | InnovationProblem solvingContradictionsCreativity | LearningOperationsImprovement |