Agentic Shift #1: From Narrow Specialists to Complete Craftspeople
Originally published on agenticshift.org ↗
TL;DR:What strikes me most is how little we talk about the organizational side: which of our structures, roles and rules have to change for the agentic times.
I've been to five conferences recently, and I'm at a sixth one right now. What strikes me most is how little we talk about the organizational side: which of our structures, roles and rules have to change for the agentic times.
So I'll try to help fill that gap, with what I see from the org design and transformation side. Starting with a short series on the agentic shifts.
Agentic Shift #1: from narrow specialists to complete craftspeople
This one feels obvious. With AI at their side, a backend developer can build the UI, write the tests and go through the customer interviews. Agents fill the specialist gaps, and the step into a new domain gets much shorter than it used to be.
But the fact that people can work broadly doesn't mean they are allowed to.
Look at the job titles. "Senior Java Developer." "Frontend Engineer." "QA Specialist." Each title is a small fence: it says what you own, what you may touch, and what will count at your next review. A Java developer who spends a sprint on the React app and the test pipeline has, on paper, done somebody else's job. And moving to a new domain often resets their seniority.
So the organizational side of AI adoption starts in an unglamorous place: career paths. Broader titles first. A Java Developer becomes a Product Developer. Frontend, backend and QA specialists become product developers with different depths.
And when a Product Developer L3 is promoted to L4, it's because she grew both deeper and broader. Importantly, not only in technology, but in the customer's domain too.
Some companies call this tailwind career paths: the career system pushes people toward the broader work instead of holding them back from it.
If your engineers already use AI to cross into new areas, what does their job title still say? Does it support them in doing the whole work, or does it keep them busy using AI to produce more output in their own narrow corner?
This text first appeared on agenticshift.org and LinkedIn.
Alexey Krivitsky
Co-author of 10X ORG and co-creator of Org Topologies. Helps organizations rethink, redesign & rewire themselves for the AI era — from the codebase to the boardroom.
As a full-stack consultant, I operate across all three layers — AI Fluency, Team Flow & Org Fit. Talk to me to get a custom offer that matches your organization’s maturity to drive the impact.