View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Sailboat RetrospectiveTeam Cognitive Load AssessmentSprint RetrospectiveAfter-Action Review
| Criterion |  Agile Sailboat Retrospective |  Team Design Team Cognitive Load Assessment |  Agile Sprint Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | 45-90 min | 60-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 4-12 | 3-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Sailboat Board, Risks, Improvement Actions | Cognitive Load Profile, Action List | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tags1 shared | RetrospectiveTeamImprovement | TeamComplexityImprovementDiagnosis | RetrospectiveImprovementLearning | LearningOperationsImprovement |