methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Team Cognitive Load Assessment with its method-specific working model.
Team Design
Team Cognitive Load Assessment
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of Spotify Model Mapping with its method-specific working model.
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 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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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
MediumLowMediumMedium
Timedifferent
60-90 min45-90 min2-4 h90-180 min
Participantsdifferent
3-123-123-125-15
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Cognitive Load Profile, Action ListExpectation Map, Alignment Notes, Agreements7S Assessment, Alignment Gaps, Change ActionsSpotify Model Map, Action List
Tagsno overlap
TeamComplexityImprovementDiagnosis
AlignmentStakeholdersTeam
OrganizationStrategyAlignmentChange
TeamOrganizationAlignmentDiagnosis
Add more methods