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 Starfish Retrospective |  Operations Root Cause Analysis |  Agile Start Stop Continue |
|---|---|---|---|---|
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 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 1-4 h | 30-60 min |
Participantsdifferent | 4-12 | 4-12 | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Starfish Board, Practice Changes, Experiments | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | RetrospectiveImprovementExperimentsTeam | Root causeProblem solvingQualityIncident | RetrospectiveImprovementTeamReflection |