View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Team Design Team Cognitive Load Assessment | ![]() Agile Starfish Retrospective | ![]() Operations Accountability Ladder |
|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-90 min | 45-90 min | 20-45 min |
Participantsdifferent | 3-12 | 4-12 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Cognitive Load Profile, Action List | Starfish Board, Practice Changes, Experiments | Ownership Reflection, Action Commitment, Coaching Notes |
Tags1 shared | TeamComplexityImprovementDiagnosis | RetrospectiveImprovementExperimentsTeam | ResponsibilityLeadershipTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






