The Next Great PM Is a Builder

For years, product management has been described as a cross-functional leadership role.

That is still true, but it is not sufficient.

The next generation of great PMs will not simply write better requirements, manage cleaner roadmaps, or run tighter stakeholder meetings. Those skills still matter, but they are increasingly table stakes. The PM role is being reshaped by AI, by faster prototyping, by more algorithmic products, and by the collapsing distance between idea, implementation, evaluation, and launch.

The best PMs of the next decade will be builders.

Not because they write every line of production code. Not because they replace engineers, designers, data scientists, or researchers.

They are builders because they can operate much closer to the work.

They can move from an ambiguous customer problem to a concrete product direction. They can reason through the system behavior. They can prototype enough to clarify the idea. They can work with engineering on architecture and constraints. They can work with data science on signals, models, ranking logic, and evaluation. They can work with design on the customer experience. They can work with analytics on success metrics, guardrails, and experiment interpretation.

They do not just coordinate the work. They shape it.

This is especially true for AI, search, personalization, recommendations, and algorithmic product experiences. In those domains, the product is not just a surface area. The product is the behavior of the system. The experience is shaped by data, models, ranking logic, feedback loops, latency, experimentation, and operational controls. A PM who only understands the UI or the business objective will not be able to lead the team deeply enough.

The future PM needs range, but range alone is not enough. AI can expand what a PM can touch. It can help with prototypes, specs, analysis, research, scenario planning, and communication. But expertise is still what gives the work depth. The best PMs will use AI to extend their reach while relying on judgment, taste, and technical understanding to decide what actually matters.

That is the profile I increasingly look for.

• A PM with strong product sense.
• A PM with real technical depth.
• A PM who understands customers, systems, data, and tradeoffs.
• A PM who can work cross-functionally without becoming a meeting router.
• A PM who can define success, design evaluation loops, interpret experiments, and make hard calls when the data is imperfect.
• A PM who can help a small, high-context team move from problem to prototype to production to learning.

This also changes what we should look for when we hire and develop product leaders.

We should ask less: “Can this person manage a roadmap?”

And ask more: “Can this person lead a builder team through ambiguity?”

• Can they identify the real problem?
• Can they reason about how the system should behave?
• Can they create artifacts that accelerate the team?
• Can they challenge weak assumptions?
• Can they understand why a model, algorithm, or product experience is failing?
• Can they connect customer value, technical feasibility, business impact, and measurable outcomes?
• Can they help the team build the right thing faster without lowering the quality bar?

The next great PM is not a mini-CEO. That metaphor was always flawed.

The next great PM is also not a prompt jockey, a project manager, or a generalist who stays above the details.

The next great PM is a builder with judgment.

Someone with enough range to move across disciplines and enough depth to be useful inside the details.

---

This writing reflects my personal perspectives on product management, AI, and content discovery. It does not represent the official position of my employer or any affiliated organization.