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 |  Growth Flywheel |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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. | Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth. | 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 60-120 min | 45-90 min | Half day |
Participantsdifferent | 5-15 | 3-8 | 3-12 | Team-Leads plus Architecture |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | GrowthRetentionConversion | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization |