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 Spotify Model Mapping | ![]() Team Design Team API | ![]() Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h workshop plus review | 90-180 min | Half day initial, dann laufend | Half day |
Participantsdifferent | 4-10 | 5-15 | Ein Team plus Stakeholder | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Strategy Map, Objective Set, Cause-Effect Hypotheses | Spotify Model Map, Action List | Team API Document | Interaction Heat Map, Agreements per Pair |
Tags1 shared | AlignmentExecutionGoalsCausality | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCommunicationService | TeamAlignmentCollaborationOrganization |



