Working · 2026-11AnecdotalGrowth opsProcess

Growth pods matrixed to functions

Organize growth as pods that each combine product, engineering, design and data, matrixed to their home functions.

Also called: growth pods, growth org

Claim and evidence

The claimUber went through the entire spectrum, but over time, came to own more and more pieces of the product.

Uber · andrewchen.com · undated

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
ProductEngineeringDesignDataGrowth pod per KPIFull experimentcycle in one team
ProductEngineeringDesignDataGrowth pod per KPIFull experiment cycle in oneteam

Each pod has the skills to run the full experiment cycle on its KPI while keeping functional standards. Structure follows the KPIs and insights rather than the other way round.

How to run it

  1. Start from the KPIs and insights
  2. Form pods with all needed skills
  3. Matrix pods to their functions for standards
  4. Choose reporting line (business unit or shared)
  5. Decide how much of the codebase growth owns

Ways to run it

Design options to test, not promised results.

  1. Option APods per KPI

    Form one pod per key metric, each with product, engineering, design and data skills.

  2. Option BMatrixed reporting

    Pod members report to their functional leads for standards while working day to day in the pod.

  3. Option CGrowing ownership

    Let pods take over more of the product over time, as Uber's growth team did.

Dated examples

  1. —

    Uber

    Chen notes the team moved along a spectrum and came to own more of the product

    “Uber went through the entire spectrum, but over time, came to own more and more pieces of the product.”
    ✓ quote checked word-for-word on the page

    andrewchen.com · undated

Does it still work?

Workingas of 2026-11

Practitioner essay, undated page; no measured outcomes. source

Risks

  • Matrix structures confuse ownership
  • No outcome data in the source

Sources

  1. andrewchen.com · Andrew Chen blog · Andrew Chen · undated
    “One common structure is to treat the Growth Team as a set of pods, each one matrixed to their respective functions.”
    ✓ quote checked word-for-word on the page
  2. andrewchen.com · Andrew Chen blog · Andrew Chen · undated
    “Begin with the KPIs, the insights you’ve generated, and then move onto execution.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (ops-ai)