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 5 Whys |
|---|---|---|---|
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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 15-30 min |
Participantsdifferent | 4-12 | 2-8 | 2-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Cause Tree, Evidence Notes, Countermeasures | Root cause notes, Countermeasures |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | Root causeTreeIncidentQuality | Root causeIncidentLeanProblem solving |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
