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 5 Whys |  Agile Starfish Retrospective |  Operations 8D Problem Solving |  Operations Root Cause Tree Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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 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 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. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 15-30 min | 45-90 min | 1-6 Wochen | 1-3 h |
Participantsdifferent | 2-6 | 4-12 | 4-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Root cause notes, Countermeasures | Starfish Board, Practice Changes, Experiments | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Cause Tree, Evidence Notes, Countermeasures |
Tagsno overlap | Root causeIncidentLeanProblem solving | RetrospectiveImprovementExperimentsTeam | QualityProblem solvingRoot cause | Root causeTreeIncidentQuality |