“I’m just the backend Java dev” is a luxury the team can’t afford anymore.
The team friction The old division of labour — backend, frontend, UX, QA, each in their lane — was a response to scarcity: nobody had time to learn all of it. Agents dissolve that scarcity. But the team’s org chart doesn’t dissolve with it. Work still queues behind the one person who “owns” a layer, the designer still waits for a dev, and the backend specialist still won’t touch the React. The silos are now slowing the team down for reasons that no longer exist.
The pattern The team agrees to operate as generalists who carry a slice end-to-end, with an agent covering the depth they personally lack. People keep their deep skill — but stop treating it as a fence. A backend dev ships the UI change with the agent; the designer adjusts the API contract. Roles become areas of leadership, not walls work has to be handed across.
Why it works with AI The agent is a credible junior in every specialty at once, so the cost of stepping outside your lane collapses. What’s left scarce is judgment and context — which travel with a person, not a silo. Removing the handoffs removes the team’s biggest queue.
Watch-outs Generalist ≠ everyone is mediocre at everything. Keep deep owners for the genuinely hard calls; drop the handoff, not the expertise. And don’t force it overnight — silos are identities, and people defend them.
Related Two people per story · Skill sharing · Plan together, work alone