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 AssessmentSprint RetrospectiveStarfish RetrospectiveSailboat Retrospective
| Criterion |  Team Design Team Cognitive Load Assessment |  Agile Sprint Retrospective |  Agile Starfish 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. | 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 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 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 | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min | 45-90 min |
Participantsdifferent | 3-12 | Scrum Team | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tags1 shared | TeamComplexityImprovementDiagnosis | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |