View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 8D Problem Solving |  Agile Sailboat Retrospective |  Operations Root Cause Analysis |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | 1-6 Wochen | 45-90 min | 1-4 h | 45-90 min |
Participantsdifferent | 4-10 | 4-12 | 3-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Sailboat Board, Risks, Improvement Actions | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | QualityProblem solvingRoot cause | RetrospectiveTeamImprovement | Root causeProblem solvingQualityIncident | RetrospectiveImprovementExperimentsTeam |