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 Team API |  Growth Flywheel |  Team Design Spotify Model Mapping |  Growth North Star Metric |
|---|---|---|---|---|
Purposedifferent | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 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 product teams track many metrics, the view of the actual customer outcome easily gets lost. A North Star Metric bundles growth, usage, and value contribution into one signal that makes the system's direction visible. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 60-120 min | 90-180 min | 1-2 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-8 | 5-15 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Team API Document | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Spotify Model Map, Action List | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | TeamAlignmentCommunicationService | GrowthRetentionConversion | TeamOrganizationAlignmentDiagnosis | GrowthMetricsAlignmentRetention |