Two years ago, a strategy consultant wrote recommendations and handed them to a product team. Now that same person describes what they want to Claude and ships a prototype.
That's not a job description change. It's what happens when AI tools reduce the cost of crossing into another discipline to near-zero. And it's quietly restructuring how organizations think about headcount.
The observation is simple but worth sitting with: the real displacement happening in knowledge work right now isn't "AI replaces human." It's "person from an adjacent department learns AI tools, absorbs two jobs, and one of those jobs disappears from the org chart."
The Lane-Crossing That's Already Happening
Here's what this looks like in practice. Strategy people describe what they want to Claude and get working code. Engineers start making product decisions because they can now prototype and test assumptions themselves, without waiting for a product manager. Product managers do their own competitive analysis and data work because AI tools put those capabilities within reach.
Each person is still doing their original job. They're just doing parts of two or three jobs now.
The person who might take your role isn't a language model running on a server. It's a smart colleague who spent six months figuring out how to use these tools and quietly absorbed your scope into their workflow.
The Roles Under the Most Pressure
The jobs most exposed in this scenario aren't the ones AI will fully automate - they're the ones that served as connective tissue between more senior people. The analyst who turns strategic direction into a brief. The coordinator who translates product decisions into engineering requirements. The specialist whose value was domain knowledge that's now accessible to anyone with a good prompt.
A strategy person who can prototype doesn't need a junior engineer to build hypothesis tests. A senior engineer who can write compelling product specs doesn't need a product manager for routine features. The headcount pressure isn't "AI did this job" - it's "one person's scope expanded to cover this job too."
None of this means everyone becomes a generalist overnight. The lane-crossing only works when someone has genuine depth in their original area. A strategy person can prototype because they have the judgment to know what's worth building - the code is execution. An engineer making product calls still needs product intuition, which takes time to develop.
What's changing is the support layer around senior people. Roles that existed primarily to execute on someone else's thinking, or to translate between teams, are under the most pressure. The uncomfortable part isn't that this is surprising. It's that it's already happening, and most org structures haven't caught up.