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 |  Operations Root Cause Tree Analysis |  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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 | Medium | Medium |
Timedifferent | 45-90 min | 1-3 h | 1-4 h |
Participantsdifferent | 4-12 | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Cause Tree, Evidence Notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | Root causeTreeIncidentQuality | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
