The PM Role Is Splitting. Which Side Are You On?

The split is already measurable

Canny's 2026 data shows AI-skilled PMs earn 28% more than their peers and save four or more hours per week on core tasks like research, specs, and synthesis. Lenny Rachitsky's State of PM Job Market report puts hiring up 12% in early 2026, but the recovery is selective. Companies are not hiring more PMs. They are hiring different PMs.

The split runs along two axes. Horizontally, "AI PM" is becoming a distinct career track with its own skills and salary band. Vertically, the PMs who spend their days in execution, sprint management, and ticket grooming are watching AI do that work faster than they can. The PMs who spend their days navigating ambiguity, influencing cross-functional decisions, and shaping strategy are becoming more valuable.

My experience is that most PMs feel this shift but don't know how to respond to it.

The operator trap

The teams I've worked with over the past year share a pattern. The PMs who built their careers on being the most organized person in the room are struggling. Not because organization doesn't matter. But because AI tools now handle the operational layer, from writing user stories to summarizing customer calls to drafting release notes, in a fraction of the time.

Harvard Business Review made a striking argument in February 2026: to drive AI adoption across the company, build PM skills. Defining problems, finding tools, experimenting, integrating. That's the strategic layer. The PMs who thrive in this new reality are the ones who can do the thinking AI can't automate: framing the right problem, making trade-offs with incomplete information, and saying no to the wrong opportunity.

Shreyas Doshi puts it well: "The best PMs are not the ones who ship the most features. They are the ones who prevent the most waste." That skill becomes more important, not less, when AI makes it faster to build things nobody asked for.

No career ladder accounts for this yet

Here's the uncomfortable part. I've looked at PM career frameworks from multiple companies and capability models from PM communities. They define levels from APM through Principal PM. Execution at the bottom, strategy at the top. Standard stuff.

None of them include AI fluency as a competency dimension.

That means most product organizations are evaluating their PMs against a model that doesn't reflect the actual work anymore. A PM who is exceptional at sprint management and stakeholder updates may score highly on the current framework while being unprepared for what the role is becoming. Meanwhile, a PM who has rebuilt their discovery workflow around AI tools may look unfocused by the old criteria.

The CPO dilemma is real: there is no template for restructuring a product team around this split. You have to build it yourself.

What I'd do if I were restructuring a team right now

If you're a CPO looking at your product team and sensing this shift, here's where I'd start. Map your PMs on two dimensions: strategic capability and AI fluency. Not as a performance review. As a diagnostic.

You'll likely find four groups. PMs who are strong on both. PMs who have strategic instincts but haven't adopted AI tools yet. PMs who are technically fluent with AI but default to execution. And PMs who are strong operators with no clear path to either dimension.

The first group leads. The second group needs AI training, not more strategy workshops. The third group needs coaching on judgment, not more tool access. The fourth group is where the honest conversations need to happen.

Start with one team. One quarter. One honest assessment. See what it reveals before you redesign the whole org.