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 8D Problem Solving | ![]() Operations Kepner-Tregoe | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | High | High | Low |
Timedifferent | 30-60 min | 1-6 Wochen | 2-8 h | 45–75 min |
Participantsdifferent | 3-10 | 4-10 | 2-8 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Problem Analysis, Decision Analysis, Risk Plan | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | QualityProblem solvingRoot cause | Problem solvingRoot causeDecisionOperations | RetrospectiveLearningReflectionTeam |



