The Shipyard Team
Organize product work as a six-capability pod of controlled chaos with sensory 'tendrils' to customers
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 3
- Confidence
- 90%
A model for structuring product teams in the AI age as a 'shipyard' — controlled chaos where underlying careful communication and high skill produce orchestrated progress. The core is a six-capability (not six-person) pod that solves a problem together, with 'tendrils' connecting it to customer-facing teams so the pod can actually feel the customer.
Origin
Oji Udezue first encountered the idea from Jeff Redford (now a VC) while at Atlassian, then developed it to a new level of clarity. Detailed in their book 'Building Rocket Ships.'
Core principles
- 01A shipyard evokes controlled chaos — what looks like Brownian motion is actually orchestrated progress underpinned by careful communication and high skill
- 02It is a capability team, not a headcount team — six capabilities, however many people each requires
- 03In the AI age, rigid rituals like standups make less sense; the pod should be in constant collaboration on the problem
- 04The pod is the 'brain' but needs 'skin' — sensory tendrils to customer-facing teams — to feel customers
- 05Roles blur: PMs do more design and engineering, engineers do more PMing, everyone builds data skills
How to run it
- 1
Assemble the six capabilities
Staff the pod for six capabilities: product management, engineering, design, user research, data/ML/AI expertise, and product marketing. Fill gaps with fractional or matrixed people if a single person can't cover a capability.
Pro tip It is 'not a person thing' — optimize for capabilities present, whether that's one fractional specialist or ten developers.
Watch out Don't read 'six-person team' literally; the number is capabilities, and staffing each varies by mission.
- 2
Run it as controlled chaos, not scheduled rituals
Let the pod communicate and collaborate continuously to solve the problem rather than defaulting to fixed ceremonies like standups, which make less sense when the build cycle is this fast.
Watch out Chaos without the underlying careful communication and high skill is just chaos — the orchestration is what makes it work.
- 3
Attach tendrils to customer-facing teams
Wire the pod to sales, customer success, and support so it can sense customers directly. Pull those people into the room before shipping.
Pro tip Oji did design reviews with a support manager present at Calendly — the support manager had had thousands of conversations and could immediately say 'that's not going to work.'
Watch out Design and engineering, however much they care, ship 'feature debt' and problems all the time without a customer-facing sensor in the room.
In the wild
Before shipping anything at Calendly, Oji ran design reviews with a support manager in the room. Because the support manager had had thousands of customer conversations, they could look at a design and immediately flag 'that's not going to work.'
→ The tendril to the support team caught shippable problems that the design and engineering teams, despite caring, would have missed.
Common mistakes
Interpreting the shipyard as six headcount
People fixate on 'six people' and object, when the model is six capabilities — staffing each is variable and can be fractional, matrixed, or many developers.
Building the pod without customer tendrils
A pod that is all 'brain' and no 'skin' ships feature debt because it can't feel the customer; connection to sales/success/support teams is what surfaces reality before launch.
Is it for you?
Best for
Product and engineering leaders restructuring teams for fast AI-era build cycles and blurring roles
Not ideal for
Tiny early-stage teams where one or two generalists already cover every capability and formal pod structure adds overhead
From the transcript
“A shipyard is to evoke controlled chaos.”
“what looks like you know, you know, Brownian motion is actually orchestrated progress”
“what a shipyard team looks like is a sixperson team. It is uh PM, it is engineering, it is design, it is user research, is…”
“think about the shipyard team is the brain but this is the skin this is how you feel customers”
“before I shipped anything at Calendarly I did the design review with a a support manager, right? A support manager had to be in the…”
From the episode
How AI is reshaping the product role
Oji and Ezinne Udezue