View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Starfish RetrospectiveA3 Problem SolvingRoot Cause AnalysisFailure Mode and Effects Analysis
| Criterion |  Agile Starfish Retrospective |  Operations A3 Problem Solving |  Operations Root Cause Analysis |  Operations Failure Mode and Effects 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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 45-90 min | 1-4 h | 2-6 h |
Participantsdifferent | 4-12 | 2-5 | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | A3 Report, Action Plan, Root Cause Analysis | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | LeanProblem solvingCoachingOperations | Root causeProblem solvingQualityIncident | RiskQualityOperationsRoot cause |