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 5 Whys |  Agile Mad Sad Glad |  Agile 4Ls Retrospective |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 15-30 min | 30-60 min | 45–75 min | 1-6 Wochen |
Participantsdifferent | 2-6 | 3-10 | Team members involved | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Root cause notes, Countermeasures | Emotion Board, Themes, Action Items | 4Ls Board, Learning Themes, Improvement Actions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Root causeIncidentLeanProblem solving | RetrospectiveTeamReflection | RetrospectiveLearningReflectionTeam | QualityProblem solvingRoot cause |