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 AssessmentSailboat RetrospectiveAccountability LadderStarfish Retrospective
| Criterion | ![]() Team Design Team Cognitive Load Assessment | ![]() Agile Sailboat Retrospective | ![]() Operations Accountability Ladder | ![]() Agile Starfish 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 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. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min | 45-90 min | 20-45 min | 45-90 min |
Participantsdifferent | 3-12 | 4-12 | 1-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Sailboat Board, Risks, Improvement Actions | Ownership Reflection, Action Commitment, Coaching Notes | Starfish Board, Practice Changes, Experiments |
Tags1 shared | TeamComplexityImprovementDiagnosis | RetrospectiveTeamImprovement | ResponsibilityLeadershipTeam | RetrospectiveImprovementExperimentsTeam |



