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 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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Purposedifferent
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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitydifferent
LowMediumMediumLow
Timedifferent
45-90 min2-4 h90-180 min60–90 min
Participantsdifferent
3-123-125-152-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, Agreements7S Assessment, Alignment Gaps, Change ActionsSpotify Model Map, Action ListStakeholder Map, Engagement Plan, Risk Notes
Tags1 shared
AlignmentStakeholdersTeam
OrganizationStrategyAlignmentChange
TeamOrganizationAlignmentDiagnosis
StakeholdersAlignmentFacilitationChange
Add more methods