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 A3 Problem Solving | ![]() Operations 8D Problem Solving | ![]() 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 a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | 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. | 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 | Medium | High | Low |
Timedifferent | 30-60 min | 45-90 min | 1-6 Wochen | 45–75 min |
Participantsdifferent | 3-10 | 2-5 | 4-10 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | A3 Report, Action Plan, Root Cause Analysis | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | LeanProblem solvingCoachingOperations | QualityProblem solvingRoot cause | RetrospectiveLearningReflectionTeam |



