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 8D Problem Solving |  Operations 5 Whys |  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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | High | Low | Low |
Timedifferent | 45-90 min | 1-6 Wochen | 15-30 min | 30-60 min |
Participantsdifferent | 4-12 | 4-10 | 2-6 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Root cause notes, Countermeasures | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamImprovement | QualityProblem solvingRoot cause | Root causeIncidentLeanProblem solving | RetrospectiveImprovementTeamReflection |