View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sprint Retrospective |  Systems Thinking CATWOE Analysis |  Operations After-Action Review |  Systems Thinking Rich Picture |
|---|---|---|---|---|
Purposedifferent | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 20-45 min | 30-90 min |
Participantsdifferent | Scrum Team | 3-8 | 3-12 | 2-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Improvement actions, Team agreements | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Lessons learned, Action items, Event summary | Rich Picture, Problem Framing Notes |
Tagsno overlap | RetrospectiveImprovementLearning | Systems thinkingFramingStakeholders | LearningOperationsImprovement | Systems thinkingSoft systemsFramingVisualization |