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 |  Agile Sprint Retrospective |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-120 min | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | 3-12 | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Lessons learned, Action items, Event summary | Improvement actions, Team agreements |
Tagsno overlap | ContradictionsInnovationProblem solving | LearningOperationsImprovement | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
