I rethought how to build a UX team in e-commerce from scratch in the AI era. What I learned flips everything.
I don't start from roles. I start from processes — how many of them today an agent does better and faster than a dedicated person. The traditional UX team was designed for a different world.
View on LinkedInThe question isn't how many people you need on a UX team. It's which processes still require a human — and which ones an agent already handles better. That reframe changes everything about how you'd staff an e-commerce UX function today.
Why the old model breaks
The traditional UX team was built for a different world. Researcher, designer, developer — each in their own lane. Endless handoffs, energy wasted coordinating instead of producing. And a manager who managed people instead of guiding a vision.
Agents now cover documentation, consistency checks, ticket creation, analytics interpretation, and first-pass content. The team structure should reflect that — not pretend it doesn't exist.
How I'd build it today
- 1 UX manager with AI skills — coordinates the team, manages agent workflows, and keeps output quality high. Doesn't delegate AI to others. Masters it first.
- 1 senior UX/UI with frontend skills — autonomous across multiple process stages, able to take an idea from wireframe to implementation without depending on continuous handoffs.
- 1 UX analyst — combines qualitative research and behavioral data, interprets funnels, identifies drop-offs, and turns what agents collect into concrete product decisions.
Three people. Focused, autonomous, built for how work actually flows now.
It's not a reduced team. It's a precise team.
Takeaway
Headcount isn't the metric — coverage is. A three-person team with agents handling the repetitive layer can outproduce a six-person team still running handoff-heavy workflows. The manager who masters AI first sets the bar for everyone else.
How would you structure it today?
