View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Rich Picture |  Agile Starfish Retrospective |  Agile Sailboat Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-90 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-10 | 4-12 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Rich Picture, Problem Framing Notes | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam |