The Pod + Product Staff Team Model
Replace the 13-person specialist team with a 6-person generalist pod plus one summoned specialist
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 90%
A team-shape framework for the AI era: collapse the traditional cross-functional 'baker's dozen' into a small pod of 4-6 generalist engineers led by a 'product staff' (an evolved PM who can also do design, data science, and research using new tools), then add exactly the one senior specialist the specific work demands. Use when restructuring product teams to move faster with fewer coordination costs.
Origin
Adam Mosseri describes the shift Instagram/Meta made 'this year' away from the canonical ~13-person specialist team toward smaller pods, driven partly by AI productivity gains but mostly by the fact that smaller teams coordinate less and make better decisions.
Core principles
- 01Small teams are more effective independent of AI — less design-by-committee, faster decisions
- 02Build the team around the needs of the work, not a fixed org chart
- 03The generalist 'product staff' absorbs the mechanical parts of design/data/research; summon a senior specialist only when the work is genuinely novel or high-stakes
How to run it
- 1
Start from a generalist core
Staff a pod with four to six engineers who are more generalist than specialist, plus one product staff who covers PM plus the routine parts of design, data science, and research.
Pro tip The product staff can now auto-pull a basic funnel/waterfall analysis with internal tools that a year ago needed a dedicated data scientist.
- 2
Add the one specialist the work needs
If the work requires pricing strategy, add a senior data scientist; if it's novel from an experience standpoint, add a very senior product designer. Match the specialist to the actual demand.
Watch out Don't default-staff every function; you might have zero data scientists, designers, or researchers on a given pod.
- 3
Keep the core small to preserve speed
End with a core of roughly six or seven people so there are fewer people to coordinate, enabling faster movement and less design-by-committee.
Watch out Still invest in growing tomorrow's senior specialists — a team of only super-senior ICs with no juniors has no pipeline and you'll regret it in a couple years.
In the wild
A traditional data-science question — a reels-creation waterfall showing where people fall off at each step — used to require bespoke data-scientist work. Internal tools now let a product staff pull it automatically.
→ The generalist product staff can do work they couldn't do a year ago, shrinking the team.
Common mistakes
Cutting all juniors from a function
If you keep only super-senior specialists and hire no new ones, you have no one growing into the next generation of senior talent.
Is it for you?
Best for
Product leaders at mid-to-large companies restructuring teams to exploit AI-driven productivity
Not ideal for
Early-stage startups that are already small and generalist by default
From the transcript
“this year it's changing we've adopted what we call pods which are just mini teams where it's call it four to six engineers who are…”
“So a PM who can do some of what a designer does and some of what a data scientist does and some of what a…”
“we try to build the team based on the needs of the work a”
From the episode
Adam Mosseri: AI is a tailwind for authenticity