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 TRIZ |  Operations Learning Review |  Operations After-Action Review |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. | 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 | High | Medium | Low | Low |
Timedifferent | 1-4 h | 1-3 h | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 2-8 | 3-10 | 3-12 | Scrum Team |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Contradiction Statement, Inventive Principles, Solution Concepts | Learning Review Notes, System Factors, Improvement Actions | Lessons learned, Action items, Event summary | Improvement actions, Team agreements |
Tagsno overlap | InnovationProblem solvingContradictionsCreativity | LearningRetrospectiveIncidentOperations | LearningOperationsImprovement | RetrospectiveImprovementLearning |