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 |  Facilitation Responsibility Poker |  Facilitation Expectation Mapping |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min | 45-90 min | 45-90 min | 90-180 min |
Participantsdifferent | 3-12 | 3-10 | 3-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Cognitive Load Profile, Action List | Responsibility Map, Role Agreements, Open Questions | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tags1 shared | TeamComplexityImprovementDiagnosis | RolesResponsibilityTeamFacilitation | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |