A PM reads that traditional product management roles are down 30%, and the headline sounds final: the profession is disappearing.

I’ve been reading the data differently. I see less evidence that the discipline is vanishing than that its work is being reassigned. The 2026 CPO Insights Report, a survey of 1,500+ product leaders from Products That Count and Mighty Capital, reported traditional PM roles down 30% across industries, with declines as steep as 70% in SaaS. The same survey found a newer “Product Builder” category, roles that blend product management, engineering, and design and ship with AI-native tooling, up tenfold over the same period.

The Shuffle in the Data

The distinction matters because PM role decline and PM professional displacement aren’t the same thing. What’s declining is the coordinator version of the role, the product manager whose value sat primarily in owning the roadmap and keeping stakeholders aligned through ceremony and information relay. What’s growing is the product professional who can scope, prototype, validate, and ship, with AI increasingly handling the translation layer that used to consume that role.

I’ve been watching this pattern develop and wrote about an early signal in October 2025, when the build/buy/skip AI decision stopped being a quarterly strategic conversation and started becoming a daily operational call. I didn’t fully anticipate how quickly the role boundary would shift to match that decision cadence.

A PM’s week used to include two days turning stakeholder notes into a requirements document, another day aligning design and engineering, then a week waiting on a prototype. In many organizations, that same work now compresses into synthesizing the research, generating a working prototype, testing it, and arriving at the engineering conversation with evidence instead of a document.

The coordination role, where the primary job was aggregating information and maintaining alignment across teams, is what the decline data is likely capturing. In many organizations, AI now handles a large share of that information synthesis, and the ceremonies that used to consume a coordinator’s attention are increasingly automated.

What’s left and growing is more specific than the coordinator role. That’s the product professional who knows which problem is worth solving before the roadmap says so, and who can evaluate competing technical approaches against real customer constraints without routing the question entirely to engineering.

Translated Skills

The managers who transitioned into builder roles brought two things that don’t compress well into AI outputs.

The first is technical fluency deep enough to evaluate what AI builds, not just prompt it. This isn’t “can write code”–it’s closer to “can read an implementation and understand the trade-offs well enough to catch when an AI-generated solution is solving the wrong version of the right problem.” I wrote about this as an edge case in November 2025 (When Product Managers Code); however, the CPO data suggests it was an early signal, not an edge.

Technical fluency doesn’t mean becoming the strongest engineer in the room. It means having enough range to inspect what the tools produce, challenge it, and learn from getting it wrong.

The second is the composite frame, the ability to evaluate a capability decision across build, buy, and augment options with enough conviction to defend it in a budget conversation. That requires enough technical range to assess actual build cost honestly, and enough product judgment to know whether a capability should be owned or borrowed. Those two things together don’t delegate cleanly.

At The Top

That shift toward technical fluency and the composite frame isn’t limited to individual contributors. The same CPO Insights Report describes movement at the top too: respondents reported strategy work rising to 74% of CPO time, roadmap work falling to 10%, and roughly a third managing an AI M&A budget directly.

Renée Niemi, resident CPO at Products That Count, frames the direction in the report: “The best will operate as portfolio-driven engines of innovation, placing bets and scaling what works as Chief Product Investors.”

Executive search reflects a similar shift. Christian & Timbers’ 2026 CPO hiring guide now lists AI fluency alongside P&L ownership as an expected CPO capability, not a differentiator. At the executive level too, the market increasingly wants judgment that spans technical depth and commercial awareness, not functional depth in one area alone.

Where This Points

I don’t think the real question is whether product managers are being displaced. Some are, specifically the ones whose primary value was coordination that AI now handles faster. A more useful question is what percentage of your current work requires judgment that can’t be synthesized, versus coordination that could run without you. Most people, if they’re honest, already know which side is larger. Now it’s time to adjust, the way we’ve adjusted through every previous technological shift.