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 Spotify Model Mapping |  Facilitation Stakeholder Salience Model |  Facilitation Stakeholder Mapping |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 | Low | Low |
Timedifferent | 90-180 min | 60-90 min | 60–90 min | 45-90 min |
Participantsdifferent | 5-15 | 3-6 | 2-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Spotify Model Map, Action List | Salience Diagram, Strategy per Class | Stakeholder Map, Engagement Plan, Risk Notes | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamOrganizationAlignmentDiagnosis | StakeholdersFacilitationAlignmentGovernance | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersTeam |