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 4Ls Retrospective | ![]() Agile Mad Sad Glad | ![]() Knowledge Modeling Feynman Technique | ![]() Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45–75 min | 30-60 min | 20-60 min | 45-90 min |
Participantsdifferent | Team members involved | 3-10 | 1 | 4-12 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items | Plain-language Explanation, Knowledge Gaps, Study Notes | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection | LearningKnowledgeUnderstanding | RetrospectiveTeamImprovement |



