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 Sailboat Retrospective |  Agile 4Ls Retrospective |  Operations Root Cause Analysis |
|---|---|---|---|
Purposedifferent | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 45-90 min | 45–75 min | 1-4 h |
Participantsdifferent | 4-12 | Team members involved | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RetrospectiveTeamImprovement | RetrospectiveLearningReflectionTeam | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
