A few weeks ago, in "PM 2027," I painted a picture of a future where AI co-pilots handle much of the tactical work, and I asked: What are you doing today to prepare for that shift?
Today, we answer that question.
This isn't a theoretical exercise anymore. The choice is simple: become an Orchestrator, or you will be replaced by one who already has.
This shift isn't just a threat; it's the single biggest opportunity for impact in our careers. I’m not saying this with hype. I’m saying this as someone who has been saying our practice evolve for 20 years. This is different.
The old model of the Product Manager as a "doer"—a master of tickets, specs, and summaries—is obsolete. The new model is about reclaiming our time and cognitive space to focus on what truly matters: driving strategy, deepening customer empathy, and delivering outcomes that have a massive impact on the business.
The Orchestrator's Mandate: Designing the Engine
Let's be clear about what we're discussing. An Orchestrator isn't just a PM who is good at using a few AI tools.
The PM Orchestrator is a systems architect.
Their primary value comes not from executing tasks, but from designing, building, and managing the intelligent engine that executes those tasks.
Think of it this way. The "Doer PM" is like a guerrilla filmmaker trying to do everything at once: they write the script, hold the camera, direct the actors, and then try to edit the footage alone. They are skilled and passionate, but they are consumed by the mechanics. The final product, however heroic the effort, is ultimately limited by their individual capacity and field of view.
The "Orchestrator PM" is the modern Film Director. A great director is not a better actor than their lead actor, nor are they a better cinematographer than their Director of Photography. Their expertise is different. It is one of holistic vision and strategic context.
The director's unique value is in seeing the entire story and guiding the specialists to serve the narrative. They step in to tell an actor why a scene requires a tone of quiet desperation instead of overt anger, connecting that moment to the character's full journey. They work with the cinematographer to frame a shot in a way that creates a specific, intended feeling that the audience may not even consciously notice.
This is the PM's new mandate. You are not better at crunching terabytes of data than a specialized AI. But you see the whole picture. You provide the strategic context that tells the AI what to analyze and why it matters for the business. You step in to take its raw output and frame it for stakeholders, translating data points into a compelling narrative that drives a critical decision. Like the director, you orchestrate the specialists—both human and AI—to create a single, cohesive, and impactful product.
This shift enables you, the Product Manager, to focus on your highest-leverage activities: setting the vision, navigating complex stakeholder relationships, asking the most insightful questions, and applying human judgment where it matters most.
Your Roadmap to AI-Powered Orchestration
Becoming an Orchestrator requires a deliberate, structured approach. To make this tangible, here is the seven-part roadmap we will explore in this series.
I’ve based this roadmap on a comprehensive set of PM activities, which covers the entire product journey from initial vision to continuous in-market optimization. For this series, however, we won't follow the traditional lifecycle order.
Instead, the order is intentional, designed to create a natural learning curve. We'll start with the areas that provide the most immediate impact with the lowest difficulty, and then build toward the most profound and strategic applications.
Here are the stages of orchestration we will explore:
Orchestrator Overview: This introductory article, setting the stage.
Orchestrating Execution & Delivery: We'll start here because it offers the quickest wins. This stage is about removing yourself as a communication bottleneck by using AI as a tireless project assistant that automates status updates and clarifies requirements, freeing up hours of your time each week.
Key activities we'll explore: Conducting sprint planning, collaborating on GTM plans, triaging incoming bugs, and providing regular progress updates to stakeholders.
Example in action: Setting up an AI agent that automatically generates a draft of your weekly stakeholder update by summarizing all the tasks completed in Jira and flagging any that are behind schedule.
Orchestrating Planning & Prioritization: Next, we'll tackle the core of your daily work. This is about grounding your roadmap in evidence, not just intuition, by using AI to connect proposed initiatives directly to customer feedback and business data.
Key activities we'll explore: Writing PRDs, creating detailed user stories, developing product roadmaps, and employing prioritization frameworks like RICE.
Example in action: Using an AI tool to automatically score features against a RICE framework by pulling the 'Reach' metric from your analytics platform and synthesizing an 'Impact' score from customer support tickets.
Orchestrating Discovery & Validation: With tactical work streamlined, we'll focus on getting to the core of customer problems, faster. You will learn how to use AI to process and synthesize vast amounts of qualitative data, helping you uncover the true, unsolved needs your users have.
Key activities we'll explore: Developing user personas, running user interviews, creating customer journey maps, and conducting formal usability testing on prototypes.
Example in action: Feeding 50 user interview transcripts into an AI and asking it to instantly identify the top three most cited pain points, complete with supporting quotes for each.
Orchestrating Go-To-Market & In-Market Management: Now we'll zoom out to coordinate a product's entire lifecycle. We'll show you how to streamline the complex set of launch activities and create a tight feedback loop for continuous, post-launch improvement.
Key activities we'll explore: Planning a beta test, overseeing product documentation, analyzing launch metrics, and systematically gathering user feedback post-launch.
Example in action: Using AI to generate first drafts of all your launch assets—from sales-enablement FAQs to user-facing release notes—based on a single Product Requirements Document.
Orchestrating Strategy & Vision: With the operational engine running smoothly, we'll focus on the most strategic work. You will learn to use AI to build a state of "always-on" market intelligence, helping you continuously detect signals from competitive moves and market trends.
Key activities we'll explore: Conducting market research, performing competitive analysis, defining your North Star Metric, and creating the product vision statement.
Example in action: Deploying an AI agent that monitors competitors' website changes, API updates, and job postings, and sends you a weekly digest summarizing their likely strategic shifts.
The First Step on the Path
This journey isn't about learning a few productivity hacks. It's about a fundamental redefinition of our value and a massive upgrade in our potential for impact. It's about evolving from a doer into a system designer.
Our journey down the Orchestrator's path starts now.
The use cases I'll share in this series are just the beginning, and I know many of you are already experimenting. If you have a compelling way you're using AI in your work, I want to hear about it—please reach out!
Stay tuned. Next up, we'll dive deep into our first topic: Orchestrating Execution & Delivery.
This part is right on, and one of the only ways left for humans to differentiate, Nacho:
"This is the PM's new mandate. You are not better at crunching terabytes of data than a specialized AI. But you see the whole picture. You provide the strategic context that tells the AI what to analyze and why it matters for the business."
And, I would add, can better understand and empathize with the customer...
Great, read, Nacho! Really insightful!