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 Rich Picture |  Operations After-Action Review |
|---|---|---|---|
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. | 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. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-90 min | 20-45 min |
Participantsdifferent | Scrum Team | 2-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Rich Picture, Problem Framing Notes | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveImprovementLearning | Systems thinkingSoft systemsFramingVisualization | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
