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 Mind Mapping |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When a topic is still unclear and too many thoughts surface at once, Mind Mapping creates an open surface for ordering them. It makes connections, subtopics, and starting points visible without fixing them too early. | 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 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 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | 90-180 min | 45-90 min | 60-90 min |
Participantsdifferent | 1-10 | 5-15 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Mind Map, Topic Clusters, Open Questions | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | Salience Diagram, Strategy per Class |
Tagsno overlap | BrainstormingIdeasMappingStructureFacilitation | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | StakeholdersFacilitationAlignmentGovernance |