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 | ![]() Facilitation Alignment 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 | 1-2 h | 1-2 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-8 | 4-12 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Team API Document | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | Alignment Map, Open Issues, Decision Questions | North Star metric, Input metric tree, Measurement cadence |
Tagsno overlap | TeamAlignmentCommunicationService | GrowthRetentionConversion | AlignmentStakeholdersStrategyFacilitation | GrowthMetricsAlignmentRetention |



