Growth Team

What is a Growth Team?

A growth team is a cross-functional group, typically a PM, engineers, a designer and an analyst, that owns a growth metric such as activation or retention and moves it through experiments across the whole product.

Updated November 2026 · 3 min read


A growth team is a cross-functional team responsible for increasing a company's users, customers or revenue by finding and improving the levers in the customer lifecycle, such as acquisition, activation, retention, referral and monetization, mainly through rapid, data-driven experiments. It typically includes a product manager, engineers, a designer and a data analyst, and often marketers. Unlike a feature team that owns a product area, a growth team owns a metric and works across the product to move it.

Growth teams became common in consumer internet companies in the late 2000s and spread to B2B software with the rise of self-serve and product-led growth. Sean Ellis is credited with coining the term "growth hacking" in 2010, and the discipline has since matured into what many companies call growth product management.

What a growth team does

  • Owns a growth metric. Usually a stage of the funnel, such as activation rate, or an overall measure such as weekly active teams or new recurring revenue.
  • Finds opportunities in data. Analyzes funnels, cohorts and user behavior to find where users drop off.
  • Runs experiments. Tests changes to onboarding, pricing pages, invitations, emails and in-product prompts, usually through A/B tests.
  • Builds growth loops. Designs mechanisms where one user's activity brings in or retains others, such as invitations and shared content.
  • Shares learning. Documents what worked and what did not, so the rest of the company benefits.

How growth teams are organized

ModelHow It WorksStrengthsChallenges
IndependentA standalone growth team with its own leader, reporting into product or a dedicated growth executiveClear focus, fast decisions, dedicated engineersCan clash with teams that own the product areas it changes
Embedded or functionalGrowth specialists sit within existing product, marketing and engineering teamsClose to product owners, fewer conflictsGrowth work competes with other priorities and can stall
HybridA central growth team sets methods and tooling, while squads own specific funnel stagesCombines focus with reachRequires clear ownership boundaries

How to set up a growth team

  1. Confirm the foundations. Growth work amplifies a product people already value. Without signs of product-market fit, experiments optimize the wrong thing.
  2. Instrument the funnel. Reliable event tracking and analytics come before experiments.
  3. Pick one metric to start. Focus on the biggest drop-off, often activation.
  4. Staff for speed. Dedicated engineers and analyst support matter more than headcount.
  5. Set an experiment process. Use a shared backlog, a prioritization method such as ICE scoring, a weekly review and a record of results.
  6. Agree on boundaries. Settle with other product teams which surfaces the growth team can change and how it coordinates.

An example

Consider a hypothetical design tool with 8,000 sign-ups a month and an activation rate of 25%, meaning 2,000 new users a month complete a first project. The company forms a six-person growth team: a product manager, three engineers, a designer and an analyst, with activation as its only goal.

The analyst finds that users who start from a template are twice as likely to activate as those who start with a blank canvas. Over six weeks, the team runs eight experiments, including a template picker at sign-up and a shorter onboarding survey. Three succeed. Activation rises to 31%, so the same 8,000 sign-ups now produce 2,480 activated users, 480 more each month without any increase in acquisition spending.

Common pitfalls

  • Chasing short-term tricks. Aggressive prompts and dark patterns can raise a metric while damaging trust and retention.
  • Testing without enough traffic. Small samples produce false winners. Check statistical power before running tests.
  • Owning too many metrics. A team responsible for everything makes little progress on anything.
  • Working in isolation. Changes made without the owning product team create friction and inconsistent experiences.

Growth teams draw on the AARRR framework, growth loops and a product experimentation framework, and they are a form of cross-functional team.

Frequently asked questions

Who is on a typical growth team?

A typical growth team includes a product manager, several engineers, a designer and a data analyst, and often one or more marketers. The team owns a growth metric rather than a product area. Dedicated engineers and analyst support matter more than overall headcount, because the team's output depends on how quickly it can run and read experiments.

How should a growth team be structured within a company?

Growth teams are commonly organized in three ways. An independent team has its own leader and dedicated engineers but can clash with feature owners. An embedded model places growth specialists inside existing teams, which reduces conflict but lets growth work stall. A hybrid model pairs a central team that sets methods with squads owning specific funnel stages.

When should a company set up a growth team?

A company is ready for a growth team once it sees signs of product-market fit and has reliable event tracking and analytics. Growth experiments amplify a product people already value, so starting earlier tends to optimize the wrong thing. Begin with one metric, usually the biggest drop-off such as activation, and agree up front which product surfaces the team can change.