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 Failure Mode and Effects Analysis |  Agile Start Stop Continue |  Operations Fishbone Diagram |
|---|---|---|---|---|
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 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. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 45-90 min | 2-6 h | 30-60 min | 30-60 min |
Participantsdifferent | 4-12 | 3-10 | 3-12 | 2-8 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | FMEA Table, Risk Priority, Mitigation Actions | Start Stop Continue Board, Improvement Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | RiskQualityOperationsRoot cause | RetrospectiveImprovementTeamReflection | Root causeQualityOperations |