View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Team Design Team API |  Growth North Star Metric |  Growth Flywheel |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | Half day initial, dann laufend | 1-2 h | 60-120 min |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 3-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Team API Document | North Star metric, Input metric tree, Measurement cadence | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | AlignmentStakeholdersTeam | TeamAlignmentCommunicationService | GrowthMetricsAlignmentRetention | GrowthRetentionConversion |