---
title: "What Is Growth Product Management?"
description: "Growth product management means owning a metric or loop, not a feature area. What a growth PM owns, the metrics that matter and a four-step first 90 days."
canonical_url: "https://builderscamp.com/guides/path/growth-product-management"
date_published: "2026-09-27"
date_modified: "2026-09-27"
author: "Andre Albuquerque"
publisher: "Builders Camp"
guide_class: "path"
---

# What is growth product management? The role, the metrics and the playbook

**TL;DR:** Growth product management is product work organised around a metric or a loop rather than a feature area: a growth PM owns a number such as activation, retention or paid conversion and runs experiments anywhere in the customer journey to move it. The first 90 days follow a fixed order: pick the retention metric, measure it with cohorts, flatten the curve, and only then scale acquisition.

## What does a growth product manager actually own?

A growth product manager owns a metric, not a part of the product. A core PM might own search, the editor or the mobile app. A growth PM owns activation rate, week 4 retention, free to paid conversion or expansion revenue, and is allowed to change any part of the product that moves it.

The [GitLab Handbook](https://handbook.gitlab.com/handbook/product/groups/growth/) is one of the few public descriptions of a growth org written by the company itself. It states: "The Growth stage is responsible for scaling GitLab’s business value." It then describes the scope as the entire customer journey "from acquisition of a customer to the flow across multiple GitLab features - and even reactivation of lost users," and splits the work into Activation, Conversion, Expansion and Adoption groups. Each of those names is a metric, not a feature.

That is the cleanest way to tell the roles apart. If your roadmap is organised by what you are building, you are a core PM. If it is organised by which number each experiment is meant to move, you are doing growth product management, whatever your title says.

## How is growth product management different from core product management?

The difference is what gets decided first. A core PM starts from a user problem and asks what to build. A growth PM starts from a number and asks where in the journey it is leaking.

| Question | Core product manager | Growth product manager |
|---|---|---|
| What do you own? | A feature area or user problem | A metric or loop across the product |
| How is the roadmap organised? | By capability and user need | By experiment, grouped by target metric |
| What does a typical week ship? | Increments of one feature | Several small tests across onboarding, invites, pricing, paywalls |
| How is success judged? | Did users adopt and value the feature? | Did the target metric move, and do you know why? |
| Who do you work with most? | Design and engineering on one area | Data, marketing and several product teams at once |

Reforge's essay on growth loops explains why the metric-first view exists. When companies split the funnel by stage, the result is familiar: "Marketing owns acquisition. Product owns retention. Sales (if B2B) owns revenue." Each team then optimises its own stage at the expense of the others. A growth PM exists partly to own the connections between stages that nobody else owns, which is why [growth loops](https://builderscamp.com/guides/other/growth-loops) are the model most growth teams plan against.

## Why does retention come before acquisition?

Because acquisition into a product that does not retain is money spent on users who leave. Andrew Chen, using Quettra data on Android apps, reported that "the average app loses 77% of its DAUs within the first 3 days after the install," and that within 30 days the average app had lost 90 percent. Those numbers come from consumer mobile apps in 2015, not from B2B software or from your product, so treat them as a warning about the default shape rather than a benchmark. What they still show is that the natural state of a retention curve is to slide toward zero, and anything you spend on acquisition before the curve stops sliding is spent on a leak.

The healthy shape is a curve that drops and then flattens, meaning some share of every cohort keeps getting value indefinitely. The [smiling retention curve](https://builderscamp.com/guides/glossary/smiling-retention-curve), where usage rises again later, is the rarer and better version. Until at least one segment of users flattens, growth work has nothing to compound on.

## What should a growth PM do in the first 90 days?

Work in a fixed order: pick, measure, flatten, then scale. Skipping ahead is the most common way new growth PMs waste their first quarter.

| Step | Weeks | What you do | What you have at the end |
|---|---|---|---|
| 1. Pick the retention metric | 1 to 2 | Define the action that shows a user got value, and how often a retained user should do it | One sentence: "a retained user does X at least Y times per Z" |
| 2. Measure it with cohorts | 3 to 5 | Build weekly or monthly cohorts on that action and slice them by acquisition channel, first-week behaviour and use case | A table showing which segments retain and which do not |
| 3. Flatten the curve | 6 to 11 | Run experiments on onboarding and activation for the segment closest to flattening | A retention curve that stops declining for at least one segment |
| 4. Scale | 12 onward | Invest in the acquisition loop that fits how retained users already behave | A loop with its own proof metric, fed by users who stay |

Take an invented example. You join a scheduling tool for small clinics as its first growth PM. Sign-ups are healthy and leadership wants more. Instead, you define a retained clinic as one that books at least 20 patient appointments a week through the tool, then build cohorts on that definition. Clinics that connect their calendar in the first session retain far better than those that do not, so your first experiments move calendar connection into the first two minutes of onboarding. Only when that cohort's curve flattens do you ask which acquisition loop to scale, and the answer (clinics referring other clinics, or search pages for each specialty and city) comes from what retained clinics already do.

The step people skip is the first. "Monthly active users" is not a retention metric for a product used daily, and "logged in" is not value. If the metric does not describe the moment a user got what they came for, every later step inherits the error. [Retention analysis for product managers](https://builderscamp.com/guides/other/retention-analysis-for-product-managers) covers how to build the cohort table in step 2.

## Which metrics belong on a growth product manager's dashboard?

Three kinds, and they do different jobs. Scale metrics are the headline numbers leadership asks about: total active users, revenue, new accounts. Health metrics explain why a scale metric moved: activation rate, retention by cohort, invite conversion, payback period. Exploratory analysis is one-off work to test a specific hypothesis, such as whether users who try a given feature in week one retain better.

Most growth dashboards get the balance wrong by showing only scale metrics, which tell you that something changed but never what. A useful growth dashboard puts one [north star metric](https://builderscamp.com/guides/other/north-star-metric-examples) at the top and the three or four health metrics that drive it directly underneath, each broken out by cohort so a change can be traced to the users who caused it. [Activation rate](https://builderscamp.com/guides/glossary/activation-rate) almost always belongs on that second row.

## How does a growth team decide which experiments to run?

With a simple, visible scoring model and a fixed weekly rhythm. The GitLab Handbook says its growth groups prioritise ideas with the ICE framework, scoring Impact, Confidence and Ease "on a scale of 1-10," and that the Growth Product Management Director runs a weekly 50 minute growth meeting to "review, prioritize, and plan experiments." The scoring is rough on purpose. Its job is to make the bets comparable and the reasoning visible, not to predict results.

The discipline that matters more than the scoring model is writing the hypothesis before the test: which metric should move, by how much, for which cohort, and what you will do if it does not. A growth team that skips this step ends up with a long list of experiments and no record of what it learned. [ICE scoring](https://builderscamp.com/guides/other/ice-scoring-framework) and [how to run an A/B test](https://builderscamp.com/guides/other/how-to-run-an-ab-test) cover both halves.

## Is growth product management just a fashionable name for optimisation?

The strongest objection is that growth work turns into button-colour testing: many small experiments on conversion steps, each worth a fraction of a percent, while the product itself does not get better. That happens, and it happens most in companies that hire a growth PM before the product retains anyone.

The objection is right about the symptom and wrong about the cause. Growth work goes shallow when it is disconnected from the product's value, and that disconnection is a sequencing mistake. Casey Winters, former growth lead at Pinterest and Grubhub, put the correct order this way in [First Round Review](https://review.firstround.com/pinterest-and-grubhubs-former-growth-lead-on-building-content-loops/): "You need to integrate a growth strategy into the product’s development from the start, and have a plan for retaining users for the long term." A growth PM who starts with retention ends up changing onboarding, pricing and the core loop, which is product work in every sense. One who starts with acquisition ends up testing buttons.

So the practical test before taking or creating a growth PM role is simple: does at least one segment of users already retain? If yes, there is something to compound. If no, the job is still finding product and market fit, and calling it growth will not change that.

## How do you learn growth product management?

Most growth PMs learn the job by owning a number on a real product, and the fastest way to get that experience is to start before you have the title: pick a retention metric for your current product, build the cohorts, and ship one experiment against the weakest segment.

For structured practice, Builders Camp's Growth for Product Managers bootcamp runs 2 weeks with 4 live sessions and 8 self-paced microlessons, directed by Andre Albuquerque. Its published syllabus covers growth foundations and north star thinking, retention and engagement loops, acquisition loops, monetization and pricing, cohort analysis, and running experiments. Its practical challenge puts you in early 2011 at Instagram, with real cohort data, a retention problem and engineering capacity for exactly one experiment. It sits in both the Product Management Starter Track and the Growth Specialist Track, which is aimed at growth product managers who own activation, retention or revenue outcomes.

The first question to answer in the new role is not which channel to scale. It is what a retained user does, and how often.

## Frequently asked questions

### What does a growth product manager do?

A growth product manager owns a business metric, such as activation, retention, paid conversion or expansion, and runs experiments anywhere in the customer journey to move it. A core product manager usually owns a feature area or a user problem instead.

### Is growth product management the same as growth marketing?

No. Growth marketing mostly works on channels outside the product, such as ads, email and SEO. Growth product management changes the product itself, for example onboarding, invite flows, pricing pages and paywalls, and works with marketing where a loop crosses into a channel.

### What metrics does a growth PM own?

Usually one primary metric from the growth model, such as week 4 retention, activation rate, free to paid conversion or net revenue retention, plus a small set of health metrics that explain why it moved. The GitLab Handbook splits its growth work into Activation, Conversion, Expansion and Adoption groups, which is a typical split.

### What should a growth PM do in the first 90 days?

Pick the retention metric that shows a user got value, measure it with cohorts, work on flattening the retention curve, and only then scale acquisition. Scaling acquisition before retention flattens means paying to fill a leaking bucket.

### Does a company need a growth PM?

Only once the product retains some users. Before retention flattens for at least one segment, a growth PM has nothing to compound, and the job belongs to whoever is finding product and market fit.

### How do growth teams prioritise experiments?

Most use a lightweight scoring model. The GitLab Handbook says its growth groups use the ICE framework, scoring Impact, Confidence and Ease on a scale of 1 to 10, and review experiments in a weekly growth meeting.

### How do you become a growth product manager?

Show that you can own a number. Run a cohort analysis on your current product, find the behaviour that predicts retention, and ship one experiment against it with a written hypothesis and result. That record is more persuasive than a growth title.

## Sources

- [GitLab Handbook: How the growth section works](https://handbook.gitlab.com/handbook/product/groups/growth/)
- [Reforge: Growth Loops are the New Funnels](https://www.reforge.com/blog/growth-loops)
- [Andrew Chen: New data shows losing 80% of mobile users is normal](https://andrewchen.com/new-data-shows-why-losing-80-of-your-mobile-users-is-normal-and-that-the-best-apps-do-much-better/)
- [First Round Review: Pinterest and Grubhub's Former Growth Lead on Building Content Loops](https://review.firstround.com/pinterest-and-grubhubs-former-growth-lead-on-building-content-loops/)

## How this guide was made

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.