Sharper PMs don't fix a broken organizational system.

There's a version of the 2026 product conversation that's genuinely exciting. AI handles the grunt work. PMs think bigger. Strategy rises to the top. Ant Murphy's recent piece makes this case well. 59% of product professionals believe strategy and business acumen are the most critical PM skills for the next two to three years.

It's a compelling direction and there's a layer worth adding.

Upgrading the PM Is One Part of the Equation

When AI absorbs the administrative load, strategic thinking becomes the differentiator. That part resonates. Where I'd build on Ant's framing is the organizational system those PMs operate inside.

Data infrastructure matters as much as individual capability. When the data is inaccessible or unreliable, PMs are still scrubbing and fact-checking instead of thinking. That problem doesn't get solved by sharper PMs. It gets solved by investing in the foundation first.

There's also a team dimension that's easy to underweight. PMs exert the most influence when they're operating in sync. The tools, the operating model, how to move through the organization together. That's what builds confidence in Product as a function. It's a team sport as much as an individual one.

The Chapter Nobody Writes.

When top down decision-making increases, the pattern I keep seeing is roadmaps shaped around the loudest customers, the biggest accounts, or a handful of strategic partnerships. You end up building for a few, not the market. A solid product planning foundation. One that connects business goals to user outcomes and gives leadership something to actually debate from, not just react to.

Then there's the piece that almost never gets talked about. Closing the loop on whether the strategy worked.

The cycle tends to look like this. Pitch delivered —> vision painted —> investment approved —> product shipped. Usage monitored for a week, maybe a month. Then the team moves on. Product strategy gets validated at the front end … research, business cases, roadmap reviews but almost never at the back end, where the real signal lives. The 'architect of impact' only means something if there's a discipline in place to measure that impact, bring it back to the table, and iterate.

Without that loop, it's just a better sounding pitch cycle.

What CPOs and Heads of Product Actually Own

Ant's advice is valuable at the PM level. The harder moves are the organizational ones. Investing in product planning, connecting business goals to user outcomes, building the conditions that let the team do the strategic work AI is supposed to free them up for.

Individual skill without organizational infrastructure isn't strategy. Speed without direction is just chaos in disguise.