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 Mad Sad Glad |  Operations Root Cause Analysis |  Agile Start Stop Continue |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | 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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-4 h | 30-60 min | 15-30 min |
Participantsdifferent | 3-10 | 3-8 | 3-12 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Start Stop Continue Board, Improvement Actions | Root cause notes, Countermeasures |
Tagsno overlap | RetrospectiveTeamReflection | Root causeProblem solvingQualityIncident | RetrospectiveImprovementTeamReflection | Root causeIncidentLeanProblem solving |