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 Starfish Retrospective | ![]() Agile Start Stop Continue | ![]() Operations 8D Problem Solving | ![]() Operations Root Cause Analysis |
|---|---|---|---|---|
Purposedifferent | 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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 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 | High | Medium |
Timedifferent | 45-90 min | 30-60 min | 1-6 Wochen | 1-4 h |
Participantsdifferent | 4-12 | 3-12 | 4-10 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | QualityProblem solvingRoot cause | Root causeProblem solvingQualityIncident |



