Product growth in marketing or management: who owns what happens after launch?

The work goes by different names. Some call it product growth or in-app product. Sometimes it is inside a classic PM role, with retention included or handed to someone else. Elsewhere it belongs to a product marketer or a product growth marketer and is called product growth marketing. I had a role where I was called “Product growth marketer / manager”, but essentially I was responsible for marketing which drives growing our user case and finding the features to do drive adoption and repeated usage, conducting user interviews plus owning the squad’s experimentation lane for in-app product growth, hence classic product management with a clear goal e.g. redesign first user’s interaction, onboarding, new dashboards and flow to unlock key product “aha” moments.

In short, a Growth PM, a product marketer and a product manager can all touch activation, adoption and retention, and the split changes from company to company. What should not change is this, though, a product manager is responsible for a product needs to know whether customers find its value, use it successfully and keep getting value from it.

That does not mean one product manager owns every channel, campaign or retention target. It means the job does not end at release.

Below is how I read the titles, where they overlap, and how I would set up ownership so that adoption does not belong to everyone and therefore no one.

Product growth job titles: the same work in different teams

There is no standard definition behind these titles. Live job postings from nine companies, read in November 2026, show the same title covering very different jobs.

At Duolingo, a Senior PM on Growth focuses on retention and daily habit features such as streaks and notifications, while monetisation sits with a separate team. At Klaviyo, the Growth team runs from onboarding and activation through self-service purchasing and billing. GitLab files its Growth Product Manager role under its marketing job families, not product.

Product marketing varies just as much. A Growth Product Marketing Manager at OpenAI leads pricing and packaging and runs lifecycle programmes for onboarding, adoption and winback. At Lovable, the growth product marketer owns messaging, and the posting says the Growth PM owns the roadmap and experiments.

None of these models is wrong. They reflect product maturity, business model and who the company already has. A job title tells you where the work sits in the org chart. It does not tell you whether anyone is looking at what customers do after launch.

What a product manager should own

Useful result and product ´aha´ moment

This is my own take on it, being responsible product management with growth inside it, as well as typical PLG work and product growth marketing.

The product manager owns product strategy, discovery, prioritisation, the experience and delivery with design and engineering. I would add adoption to that list without hesitation.

Marty Cagan at SVPG argues that product teams should be measured on outcomes rather than output. A feature nobody uses is output. If I ship a reporting view and customers carry on exporting to a spreadsheet, the release happened but the outcome did not.

So the PM should be able to answer a few plain questions about their area:

  • Do the right customers discover the capability, and at what moment in their workflow?

  • Do they complete the task it was built for, or abandon it halfway?

  • Do they come back to it, and does that change whether they stay or pay?

What a Growth PM typically does

A Growth PM goes deeper on the mechanisms that connect people to value across the journey: activation, conversion, engagement, monetisation and retention, usually with a steady rhythm of experiments.

Casey Winters wrote on his blog that growth teams connect people to value that already exists. They work on onboarding, notifications and conversion, while retention mostly comes from the core product. So the core PM is already in the growth business.

A dedicated growth team makes sense when there is enough traffic to run experiments, a self-serve journey to improve, and journeys that cross several product areas. Before that, the work usually sits with the PM and the founder.

What product marketing contributes

Product marketing owns positioning, messaging, launches, sales enablement and much of the communication that helps people adopt a product. The Product Marketing Alliance includes demand, adoption and retention in its own definition, so overlap with product is built in.

The useful distinction is between what the product says and what the product does. Product marketing shapes how a capability is explained, to whom and when. The PM and designer own the in-product experience that the explanation leads to.

What a growth product marketer might own

A growth product marketer can sit across acquisition, lifecycle messaging, self-serve conversion and product-led growth, or own only the words inside those journeys.

It helps to separate the strategy from the job title. Product-led growth, as ProductLed defines it, treats the product as the main way to acquire, activate and retain customers. Growth marketing works mainly through channels, campaigns and budgets. A company can do both, and the people doing them need to agree where the product ends and the campaign begins.

Where ownership overlaps

I would not pretend there is one universal RACI. A common split looks roughly like this, but changes may happen, of course:

  • Product strategy and roadmap prioritisation: the PM typically leads. Growth PM and product marketing collaborate.

  • Customer research

    The product manager and product marketing both lead parts of it. PM focuses on problems and workflow, product marketing on buyers and positioning.

  • Onboarding and activation

    The PM or Growth product manager leads the experience. Product marketing collaborates on messaging. This varies most with company size. I personally think that a growth product manager is best suited for this work due to growth mechanisms and product experimentation.

  • Feature adoption

    The product manager leads in-product adoption. Product marketing leads adoption communication.

  • Pricing and monetisation

    Here it varies widely. It sits with product marketing at some companies and with the growth team at others.

  • Lifecycle messaging:

    Here product marketing or lifecycle marketing typically leads. The product manager collaborates on triggers and timing. Often times it is a part of the product growth manager work as well. For example, I have done specific triggers based on in-app work in Intercom for a client who we´ve worked on a product growth engagement.

  • Retention

    This is definitely a shared outcome. The core PM shapes it through the product, and customer success or account management shapes it through the relationship.

  • Experimentation and product analytics

    This varies heavily. The product analysis where you have one or the growth manager where one exists. The PM and data team collaborate. It´s important to note that your product analyst may get data, but not insights or actions out of it.

Why subscription products make this more important

In a subscription business the customer decides again every month or year. A shipped feature that customers never adopt does not reach that decision at all.

On top of it, the acquisition may follow, but an acquired customer is not a lifetime customer value by default. It´s crucial to maximise the value as much as

Sales can close the deal and account management owns the relationship, but adoption often shapes whether the account renews. In a self-serve product it is even more direct. One in-app behaviour can tell you a lot (does your child finish the maths exercise they started two minutes ago, or ask for the next activity?), and that is a real product or growth decision.

So activation and meaningful usage should influence the roadmap, not only the growth team's backlog. If a capability is adopted by few of the customers it was built for, that is a signal for prioritisation, just like a feature request.

My perspective from product work and some specific product growth initiatives:

B2C AI subscription

On a B2C AI interview platform, my work covered onboarding, paywalls and the customer journey from trial to paid.

Hospitality SaaS

When I worked on a performance analysis application for hoteliers, I ran UX research and usability testing, including interviews with hoteliers.

B2C EdTech

In my work for a children's B2C story-writing digital product, I worked from an early idea to launch. I mapped the journeys for children, parents, teachers and publishers, and scoped the MVP around the child's workspace, where a story is written and illustrated. We released it to beta testers in increments, so each release gave them something complete to use, and user testing fed into the next one. After launch, I built product-led growth loops for the first segment, homeschooling families, and researched schools as a possible next segment.

Here is the model I would start with and adapt:

  1. The PM owns the product experience and the product outcomes in their remit.

    That includes adoption and meaningful usage of what they ship.

  2. A Growth product marketer / manager specialises in cross-journey mechanisms, such as onboarding, upgrade moments and re-engagement, where no single product area owns the journey (since often times it is very tech-heavy).

  3. Product marketing owns or co-owns positioning, adoption communication and go-to-market.

  4. Engineering, design, data, customer success and marketing bring specialist expertise and their own signals about what customers do.

  5. Every shared metric gets an explicit decision owner. A simple agreement like Atlassian's DACI names one approver per decision, which is far better than collective responsibility.

Frequently asked questions

What is the difference between a product manager and a growth product manager?

A product manager owns a product area, its strategy and its outcomes. A growth PM focuses on the mechanisms that move people through the journey, such as activation, conversion and retention, usually through experiments.

Who owns product adoption?

The PM owns in-product adoption of what they ship. Product marketing usually owns adoption communication. In a strong team they agree on one adoption measure per capability.

Does product marketing own onboarding?

Usually not the experience itself. Product marketing often owns the messaging and lifecycle communication around onboarding, while the PM or Growth PM owns the flow.

Conclusion

Whatever the titles in your team, someone needs to own what happens after launch, and the product manager cannot step out of that because another team has "growth" in its name. The title matters less than the job itself.

If you want help setting up ownership for activation, adoption and retention, I work on product growth and monetisation and as a fractional product manager.

Next
Next

Website product management: How to manage your website as a customer-facing product