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 North Star Metric | ![]() Facilitation Expectation Mapping | ![]() Growth Flywheel | ![]() Engineering Goal Question Metric |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | 45-90 min | 60-120 min | 90-180 min |
Participantsdifferent | 3-8 | 3-12 | 3-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | North Star metric, Input metric tree, Measurement cadence | Expectation Map, Alignment Notes, Agreements | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog | GQM Table, Metric Profiles |
Tagsno overlap | GrowthMetricsAlignmentRetention | AlignmentStakeholdersTeam | GrowthRetentionConversion | MetricsMeasurementEngineeringAlignment |



