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 Sprint Retrospective | ![]() Agile Mad Sad Glad |
|---|---|---|---|
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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min |
Participantsdifferent | 3-12 | Scrum Team | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Improvement actions, Team agreements | Emotion Board, Themes, Action Items |
Tagsno overlap | TeamComplexityImprovementDiagnosis | RetrospectiveImprovementLearning | RetrospectiveTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






