View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Map |  Team Design Team Topologies Interaction Modes |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | A Strategy Map translates strategy into a few connected objectives across perspectives such as finance, customers, processes, and learning. This makes visible which capabilities and activities are meant to drive which results. | When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 2-4 h workshop plus review | Half day | 90-180 min | 45-90 min |
Participantsdifferent | 4-10 | Team-Leads plus Architecture | 5-15 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Interaction Heat Map, Agreements per Pair | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | AlignmentExecutionGoalsCausality | TeamAlignmentCollaborationOrganization | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam |