View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Starfish RetrospectiveTeam Cognitive Load AssessmentAfter-Action ReviewSailboat Retrospective
| Criterion |  Agile Starfish Retrospective |  Team Design Team Cognitive Load Assessment |  Operations After-Action Review |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 a team juggles too many domains, systems, or handoffs, it measures mental overload as an organizational problem. It clarifies responsibility, interaction, and load between teams. The result is captured as a cognitive-load profile and action list. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 60-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 4-12 | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Cognitive Load Profile, Action List | Lessons learned, Action items, Event summary | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | RetrospectiveImprovementExperimentsTeam | TeamComplexityImprovementDiagnosis | LearningOperationsImprovement | RetrospectiveTeamImprovement |