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 Fishbone Diagram |  Operations Failure Mode and Effects Analysis |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 30-60 min | 2-6 h | 30-60 min | 45-90 min |
Participantsdifferent | 2-8 | 3-10 | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | Root causeQualityOperations | RiskQualityOperationsRoot cause | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |