View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Customer Journey Mapping | ![]() Engineering Goal Question Metric | ![]() Growth North Star Metric | ![]() Growth Flywheel |
|---|---|---|---|---|
Purposedifferent | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 90-180 min | 1-2 h | 60-120 min |
Participantsdifferent | 4-10 | 3-6 | 3-8 | 3-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | GQM Table, Metric Profiles | North Star metric, Input metric tree, Measurement cadence | Flywheel Map, Friction Points, Growth Levers, Experiment Backlog |
Tagsno overlap | JourneyServiceService design | MetricsMeasurementEngineeringAlignment | GrowthMetricsAlignmentRetention | GrowthRetentionConversion |



