View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Decision Making Force Field Analysis |  Business Strategy McKinsey 7S |  Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 45-90 min | 2-4 h | 90-180 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Force Field Map, Change Levers, Risk Notes | 7S Assessment, Alignment Gaps, Change Actions | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCommunicationService | ChangeDecisionStrategy | OrganizationStrategyAlignmentChange | TeamOrganizationAlignmentDiagnosis |