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 | ![]() Agile Starfish Retrospective | ![]() Facilitation Expectation Mapping | ![]() 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. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 45-90 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-10 | 4-12 | 3-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Starfish Board, Practice Changes, Experiments | Expectation Map, Alignment Notes, Agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RetrospectiveTeamReflection | RetrospectiveImprovementExperimentsTeam | AlignmentStakeholdersTeam | RetrospectiveLearningReflectionTeam |



