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 | ![]() Operations Root Cause Analysis | ![]() Operations 8D Problem Solving | ![]() 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 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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 | Medium | High | Low |
Timedifferent | 45-90 min | 1-4 h | 1-6 Wochen | 30-60 min |
Participantsdifferent | 4-12 | 3-8 | 4-10 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | Root causeProblem solvingQualityIncident | QualityProblem solvingRoot cause | RetrospectiveImprovementTeamReflection |



