View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Growth Hooked Model |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design. | 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 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 | Multiple workshops over several weeks | 90-180 min | 45-90 min | Half day |
Participantsdifferent | 2-8 | 5-15 | 3-12 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | GrowthBehaviorRetention | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization |