View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Stakeholder Salience Model | ![]() Business Strategy McKinsey 7S | ![]() Facilitation Expectation Mapping | ![]() Team Design Spotify Model Mapping |
|---|---|---|---|---|
Purposedifferent | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 60-90 min | 2-4 h | 45-90 min | 90-180 min |
Participantsdifferent | 3-6 | 3-12 | 3-12 | 5-15 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Salience Diagram, Strategy per Class | 7S Assessment, Alignment Gaps, Change Actions | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List |
Tags1 shared | StakeholdersFacilitationAlignmentGovernance | OrganizationStrategyAlignmentChange | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis |



