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 | ![]() Agile Mad Sad Glad | ![]() Agile Start Stop Continue | ![]() Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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. | 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 | Low | Low | High |
Timedifferent | 30-60 min | 30-60 min | 30-60 min | 2-6 h |
Participantsdifferent | 2-8 | 3-10 | 3-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Fishbone Diagram, Cause Categories, Investigation Backlog | Emotion Board, Themes, Action Items | Start Stop Continue Board, Improvement Actions | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityOperations | RetrospectiveTeamReflection | RetrospectiveImprovementTeamReflection | RiskQualityOperationsRoot cause |



