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 the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Spotify Model Mapping with its method-specific working model.
Team Design
Spotify Model Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
2-4 h30 min Setup, dann laufend90-180 min45-90 min
Participantsdifferent
3-121-3 maintaining, briefing for everyone5-153-12
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
7S Assessment, Alignment Gaps, Change ActionsRAID Log, Status Report SourceSpotify Model Map, Action ListExpectation Map, Alignment Notes, Agreements
Tagsno overlap
OrganizationStrategyAlignmentChange
RiskTrackingStakeholdersGovernance
TeamOrganizationAlignmentDiagnosis
AlignmentStakeholdersTeam
Add more methods