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 |  Team Design Team Topologies Interaction Modes |  Growth Flywheel |
|---|---|---|---|
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 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. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 90-180 min | Half day | 60-120 min |
Participantsdifferent | 5-15 | Team-Leads plus Architecture | 3-8 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Interaction Heat Map, Agreements per Pair | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | TeamAlignmentCollaborationOrganization | GrowthRetentionConversion |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
