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 Expectation Mapping |  Team Design Spotify Model Mapping |  Decision Making Force Field Analysis |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 90-180 min | 45-90 min | 60–90 min |
Participantsdifferent | 3-12 | 5-15 | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Spotify Model Map, Action List | Force Field Map, Change Levers, Risk Notes | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AlignmentStakeholdersTeam | TeamOrganizationAlignmentDiagnosis | ChangeDecisionStrategy | StakeholdersAlignmentFacilitationChange |