View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Team Cognitive Load AssessmentAfter-Action ReviewSprint RetrospectiveSailboat Retrospective
| Criterion |  Team Design Team Cognitive Load Assessment |  Operations After-Action Review |  Agile Sprint Retrospective |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 20-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | Scrum Team | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Lessons learned, Action items, Event summary | Improvement actions, Team agreements | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | TeamComplexityImprovementDiagnosis | LearningOperationsImprovement | RetrospectiveImprovementLearning | RetrospectiveTeamImprovement |