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 | ![]() Growth Flywheel | ![]() Team Design Team Topologies Interaction Modes | ![]() Facilitation Expectation Mapping |
|---|---|---|---|---|
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. | 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 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Multiple workshops over several weeks | 60-120 min | Half day | 45-90 min |
Participantsdifferent | 2-8 | 3-8 | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | GrowthBehaviorRetention | GrowthRetentionConversion | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam |



