The AI Team Antipattern
Centralizing your AI talent into a dedicated team feels organized and intentional. It's also one of the fastest ways to kill momentum.
A lot of companies build an “AI team.” Hire a few ML engineers, maybe a data scientist or two, point them at the hardest problems, and wait for results.
It sounds reasonable. You’re concentrating expertise. You’re moving fast.
Except the team ships almost nothing that sticks.
Why centralized AI teams stall
The problem isn’t the people. It’s the structure.
A centralized AI team sits outside the product teams. That means they don’t own the roadmap, don’t feel the customer pain, and don’t control the data pipelines they depend on. Every project requires negotiating access, aligning on requirements, and handing off to engineers who weren’t in the room when the model was built.
The handoff is where most of it dies.
Product teams see the AI team as a service bureau. The AI team sees product teams as stakeholders who don’t really understand the work. Neither is wrong — but that gap doesn’t close on its own. It widens, slowly, until the AI team is producing internal demos and the product teams have stopped waiting for them.
What embedding actually looks like
Embedded AI means one or two ML-capable people sit directly inside a product team. They attend the standups. They read the support tickets. They know why the pipeline broke last Thursday.
They build things that work because they understand the context firsthand — not through a PRD, not after a kickoff meeting three weeks after the idea was born.
The objection you’ll hear: “We can’t afford to split our small AI team across every product pod.” That’s real. But a centralized team that ships one internal demo per quarter is more expensive than it looks — in time, in opportunity cost, and in the slow credibility drain that comes with it.
When centralization does make sense
Not never. Centralize the shared infrastructure: model registry, evaluation frameworks, observability tooling, the data platform. These are cross-cutting concerns that genuinely benefit from shared ownership and don’t belong inside any single product team.
Centralize the platform, not the product work. Application-level AI — the thing that actually creates user value — belongs close to the product.
The test
Ask your AI team: what’s the last thing they shipped that a real user touched? How long did it take from idea to production?
If the answers are vague or the timelines are embarrassing, the structure is probably the problem — not the talent.
Reorganizing is harder than hiring. But it’s the actual fix.
The “AI team” makes perfect sense on a slide. In practice, distance from the product is distance from the outcome.