Why Your AI Center of Excellence Will Fail
TL;DR:
---
The CoE Trap
Enterprise playbook: Create a dedicated AI team. Hire PhDs. Build infrastructure. Announce initiatives. Watch the organization stay exactly the same.
The problem isn't the team—it's the structure. Centers of Excellence are by definition separate from the work. Your CoE researches "the future of AI adoption" while product teams ship features the old way. They become advisory bodies. And nobody listens to advisors.
The parallel everyone misses: companies that dominance distribution (Amazo Logistics, Tesla Manufacturing, Netflix Encoding) didn't create Centers. They embedded the capability into every team that touches customers. AI should work the same way.
---
Why Teams Build CoEs (And Why They Regret It)
Centers of Excellence exist because:
- Fear of spreading incompetence — "If we let product teams touch AI, they'll waste money"
- Org structure inertia — easier to create a new department than restructure existing ones
- Resume-building — executives want a VP of AI on the org chart
But the result is predictable:
- CoE spends 18 months building a "platform" nobody uses
- Product teams can't wait, build their own AI integrations (worse, duplicated)
- CoE blames product teams for not adopting; product teams blame CoE for slow delivery
- Actual progress stalls
The companies winning with AI aren't the ones with fancy CoE structures. They're the ones where a product team can integrate Claude or GPT in a sprint, iterate with real users, and own the outcome.
---
The Embedded Alternative
Skip the Center. Instead:
- Hire 2-3 AI engineers (not 20). Put them inside product teams.
- Give product leaders budget for AI experiments. Not gated through a committee.
- Build internal tooling (monitoring, cost tracking, safety checks). Make it self-serve.
- Create async docs (not weekly sync meetings). How to integrate APIs, common pitfalls, what works.
- Let teams fail fast. Most AI bets won't work. That's feature discovery, not failure.
This isn't "no governance." It's governance that moves at product speed, not academic speed.
---
What Actually Works
The pattern we see in enterprises shipping AI fast:
- AI capability lives inside product teams
- They own the ROI (not the CoE)
- Shared infrastructure and guardrails (not shared theology)
- Async knowledge-sharing (not tribal knowledge)
One company went from "CoE explored 5 AI ideas in 2 years" to "product teams shipped 30 AI features in 1 quarter" after embedding engineers directly.
CoE: nice org chart. Real progress: messy, distributed, team-owned.
---
What We've Learned
If you're building AI capability in an enterprise:
- Don't create a separate team. Embed the skill.
- Give product teams autonomy to experiment.
- Build infrastructure, not ideology.
- Measure success by shipped features and revenue impact, not research papers.
Your best AI strategy isn't a Center of Excellence. It's making every team excellent at AI.
---
Sources
- "How Netflix Scales Innovation" — Culture as competitive advantage, not org structure
- "The Innovator's Dilemma" (Clayton Christensen) — Why separate innovation units fail
- Anthropic's approach to capability distribution — Embedded patterns vs. gated access
- Real case study: Fintech firm that dissolved CoE, went product-embedded (4x AI adoption)