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 |  Business Strategy Value Chain Analysis |  Facilitation Expectation Mapping |  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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever 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. | 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 | High | Low | Medium |
Timedifferent | Half day initial, dann laufend | Half day | 45-90 min | 90-180 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-8 | 3-12 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Value Chain Map, Lever List | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tagsno overlap | TeamAlignmentCommunicationService | StrategyBusiness modelDiagnosisAnalysis | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |