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 Learning Review | ![]() Agile 4Ls 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 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. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-120 min | 1-3 h | 45–75 min |
Participantsdifferent | 2-8 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Contradiction Statement, Abstraction Notes, Solution Principles, Concept Ideas | Learning Review Notes, System Factors, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ContradictionsInnovationProblem solving | LearningRetrospectiveIncidentOperations | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






