Everyone keeps asking whether AI favors specialists or generalists.
I think that is the wrong question.
AI does not pick a side. It changes the tradeoff.
The old world forced a choice. You could go deep, or you could go wide. Specialists had depth. They knew the product, the function, the domain, the process, the edge cases, and the hard-earned lessons that only come from living inside a problem space for a long time. They could answer the hard question inside their lane.
Generalists had range. They could connect dots across teams, customers, markets, functions, and business models. They could see patterns others missed. They could translate between groups that did not naturally speak the same language.
Both were valuable.
Both were incomplete.
The specialist often got trapped inside a narrow lane. The generalist often lacked the depth to make the hard call. That tradeoff shaped the modern org chart more than we admit.
A lot of organizational design was built around the limits of human range. No one person could hold enough context, expertise, policy, technical detail, customer nuance, and judgment to move complex work all the way through. So we created handoffs.
The business person handed off to the technical person.
The technical person handed off to the product person.
The product person handed off to the legal person.
Legal handed it to security.
Security handed it to IT.
IT handed it back with three comments and a meeting invite.
Very sophisticated. Also very slow.
That is the part AI changes most.
AI does not make specialization irrelevant. It does not magically make everyone a great generalist either. AI attacks the handoff tax.
It gives specialists more range.
It gives generalists more depth.
It lets more people move work farther before another human needs to get involved.
That last part matters.
The goal is not to eliminate experts. The goal is to stop using experts as routing infrastructure.
AI changes how work should move
Take a simple example: enablement content.
In the old model, the person responsible for the content might need input from product, legal, IT, security, field enablement, and several other teams before the work even becomes coherent. Some of that approval is real. You still need Legal where legal approval is required. You still need Security where security approval is required. You still need a true product expert when the answer matters.
But a lot of the back and forth is not judgment. It is translation. It is first draft review. It is basic risk identification. It is asking someone else to do the thinking the owner could have done before the handoff.
With AI, that content owner should be able to do much more before involving anyone else. They should be able to draft the content, compare it against policy, pressure test the messaging, identify possible legal concerns, check technical claims, and prepare a cleaner approval package.
The expert still approves. But now the expert is being used for judgment, not cleanup.
That is the shift.
AI does not remove the need for depth. It reduces the dependency created by not having immediate access to depth.
This sounds subtle, but it is not. It changes the operating model. If more people can carry more context, then work should not need to move through the same number of human checkpoints. If first-pass analysis is cheap, experts should not be spending their time fixing half-baked inputs. If coordination cost falls, teams should not preserve old routing paths just because those paths are familiar.
A lot of what we call collaboration is just latency with better manners.
AI forces us to be more honest about that.
Specialists still matter, but depth needs range
This is why I do not buy the simple argument that the future belongs to generalists.
It sounds good. It is also incomplete.
A shallow generalist with AI is still shallow. They may just become faster at producing confident nonsense, which is not exactly the revolution we were promised.
Depth still matters. In fact, depth may matter more because AI makes surface-level fluency cheap. Anyone can ask AI to summarize a topic. Anyone can generate a decent first draft. Anyone can sound informed for five minutes.
The differentiator becomes whether you know enough to spot what is missing.
That is where expertise shows up.
The expert knows which detail is wrong. The expert knows which assumption is dangerous. The expert knows when the answer sounds right but will fail in the real environment.
AI raises the floor. It does not erase the ceiling.
But the specialist has to change too.
Depth without range becomes a bottleneck. If your value is only that you know one thing and everyone has to wait for you to answer it, AI is coming directly for that model.
The best specialists will not just protect their lane. They will expand from it. They will use AI to understand the surrounding business context, adjacent systems, customer implications, competitive dynamics, implementation constraints, and operational risks.
I think about my doctor. He is a TMJ specialist — decades inside one narrow, hard problem. The kind of depth you cannot fake and cannot rush.
He has had product ideas for years. Things only someone who lives inside that problem would think to build. But the ideas always died in the same place. Not because the idea was wrong. Because everything around the idea required a different expert. Ingredient research. Regulatory approval. Manufacturing. Patent filings. Legal. Each one a handoff to someone he did not have, could not afford, or did not know how to start a conversation with.
So the ideas stayed ideas.
That changed. Not because he became a chemist or a patent attorney — his depth is still in the jaw, not in IP law. But now he can do the first pass himself. Research the ingredients. Map the regulatory path. Understand what a patent filing actually involves before he ever pays someone to file one. He can carry the idea far enough to know whether it is real.
He still needs the patent lawyer. He still needs the regulatory expert. But now they get pulled in for judgment, on a thought-through idea — not to teach him the basics or route him to the next person.
His expertise was never the bottleneck. The bottleneck was access to everyone else's.
Their depth becomes the anchor.
AI expands the radius.
Generalists still matter, but range needs earned depth
The same is true for generalists, but in reverse.
The best generalists will not just float above the work connecting dots. They will use AI to go deep when the problem demands it. They will test assumptions. Build prototypes. Read the documentation. Analyze the data. Understand enough of the architecture to know where the real constraint is.
Their range becomes the advantage.
AI gives them depth on demand.
So the future profile is not specialist or generalist. It is range and depth on demand.
Go wide when the problem requires connection.
Go deep when the decision requires expertise.
Know when AI is enough.
Know when a human expert is required.
Know when the work is ready for approval and when it is still a half-baked mess wearing a nice outfit.
That judgment is the job.
Leaders need to redesign the work
This has big implications for leaders.
If your operating model still assumes every question needs to route through five humans, you are not AI native. You are just slower with better tools.
If every team is waiting on another team to move basic work forward, you have not redesigned the work. You have added AI to the same old dependency chain and called it transformation. That is not strategy. That is procurement with a keynote.
The question leaders should ask is not only, "How do we make everyone more productive?"
That is too vague.
The better question is: where are we using humans as handoffs instead of judgment?
That question exposes the waste.
It shows where experts are being pulled into low-value review. It shows where generalists are coordinating work they could now move themselves. It shows where specialists are waiting for context they could now generate. It shows where teams are protecting old process instead of redesigning the flow.
This is the real leadership work. Not buying tools. Not announcing pilots. Not celebrating usage metrics that say very little about whether the work changed.
The work has to be redesigned around a new assumption: more people can now carry more context.
That means some handoffs should disappear. Some approval paths should get cleaner. Some roles should expand. Some processes should be deleted. Some experts should be protected from low-value work so they can focus on the decisions that truly require expertise.
That is uncomfortable because handoffs are not just process. They are also identity, control, and risk management. Teams build power around being the required stop in the workflow. Leaders build comfort around knowing every risk has an owner somewhere else.
AI pressures all of that.
It asks a harder question: if the work can now move differently, why are we still organized this way?
Talent should be evaluated differently
This also changes how we should think about talent.
The old hiring and development model rewarded static expertise. What do you know? Where have you worked? What products have you covered? What functions have you supported?
Those things still matter, but they are no longer enough.
The new question is: what can you figure out, build, validate, and move without waiting for the organization to hand you a playbook?
That is a different profile.
Builder proof beats pedigree.
Show me what you built. Show me how you got stuck. Show me where the AI was wrong. Show me how you recovered. Show me how you connected the technical decision to the business outcome.
That tells me more than a polished answer about transformation.
The people who tinker are going to compound faster than the people who wait for training. That may sound harsh, but I think it is true.
Training tells you what the organization already knows. Tinkering shows you what is now possible.
In an AI world, the gap between those two things is massive.
The person experimenting with agents, prototypes, workflows, code, content, and data will develop instincts the formal enablement program cannot keep up with. They will know where the tools are strong. They will know where they break. They will know what can now be done in an hour that used to take two weeks.
That instinct becomes a leadership skill.
Not because everyone needs to become an engineer.
Because everyone needs to understand what work costs now.
The cost of drafting changed.
The cost of analysis changed.
The cost of prototyping changed.
The cost of learning changed.
The cost of coordination should change too.
If the cost of doing the work drops but the organization keeps the same handoffs, the bottleneck is no longer capability. It is muscle memory.
That is the dangerous part.
Most companies will not fail because they lack AI tools. They will fail because they bolt AI onto a process that should not exist anymore. They will use AI to make the old workflow faster, when the real opportunity is to delete half the workflow.
Architecture still matters
There is one more piece that matters: architecture.
Range and depth on demand only work if people and agents have trusted context. If the data is stale, fragmented, poorly permissioned, or disconnected from the workflow, AI just helps people move faster in the wrong direction.
That is not leverage. That is chaos with a nicer interface.
The person using AI needs access to the right information, the right tools, the right guardrails, and the right escalation paths. Otherwise, they cannot safely move the work farther. They can only generate more artifacts, faster.
This is why AI strategy cannot be reduced to prompt training or tool adoption. The architecture underneath matters. The data model matters. The permission model matters. The workflow integration matters. The escalation path matters.
If those pieces are missing, AI becomes a productivity theater machine. Lots of output. Not enough movement.
The new skill
This is not just a career conversation. It is an operating model conversation.
How should work move when more people can carry more context?
How should experts be used when first-pass analysis is cheap?
How should teams be designed when coordination cost falls?
How should leaders evaluate talent when knowledge can be generated but judgment still has to be earned?
I keep coming back to this:
The old org chart was built around the limits of human range.
AI changes those limits.
That does not mean everyone becomes the same. It means the boundaries between roles become more fluid.
Specialists need range.
Generalists need depth.
Experts still matter, but they should be used for judgment, not basic routing.
Generalists still matter, but they need enough depth to move from pattern recognition to real execution.
Leaders still matter, but they need to redesign the work instead of celebrating productivity gains inside a broken model.
The winners will be the people who know when to go wide, when to go deep, and when another human actually needs to be involved.
That is the new skill.
Range and depth on demand.
