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 Start Stop Continue | ![]() Agile Sailboat Retrospective | ![]() Operations Root Cause Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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 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 | 30-60 min | 45-90 min | 1-4 h |
Participantsdifferent | 3-12 | 4-12 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






