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 Process Mapping | ![]() Agile Starfish Retrospective | ![]() Operations After-Action Review |
|---|---|---|---|---|
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. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-3 h | 45-90 min | 20-45 min |
Participantsdifferent | 3-10 | 3-10 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Emotion Board, Themes, Action Items | Process Map, Handoff List, Improvement Backlog | Starfish Board, Practice Changes, Experiments | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveTeamReflection | ProcessOperationsImprovement | RetrospectiveImprovementExperimentsTeam | LearningOperationsImprovement |



