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 Sailboat Retrospective | ![]() Systems Thinking CATWOE Analysis | ![]() 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 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. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 2-10 | 4-12 | 3-8 | Team members involved |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Rich Picture, Problem Framing Notes | Sailboat Board, Risks, Improvement Actions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | Systems thinkingSoft systemsFramingVisualization | RetrospectiveTeamImprovement | Systems thinkingFramingStakeholders | RetrospectiveLearningReflectionTeam |



