There are countless posts right now on how PMs can use AI to boost productivity: writing better PRDs, summarizing meetings, automating backlog grooming. This isn’t one of those posts.
This is about the craft of product management itself. About how the role of the PM is evolving in real time, and why AI is collapsing the boundary between strategy and execution. What I’m sharing here is not a playbook to get 10% more efficient- it’s an observation of what’s happening in the market, and how I believe the PM craft will shift in the years to come.
Historically, PMs lived in documents and slides. We framed the why and the what, while engineers delivered the how. But this gap often slowed us down. A promising idea could sit idle for weeks before being made real.
AI is changing that.
Today, PMs can move from idea to artifact far more quickly. With the right tools, you can create prototypes, explore technical trade-offs, and even ship small fixes without blocking engineering bandwidth. This doesn’t make PMs engineers- but it does make us better builders.
Evolve your PM Craft
This shift isn’t about productivity shortcuts; it’s about craft evolution. Here’s how PMs of different archetypes can put AI into action:
1. Prototype First Move beyond slides. Build something small and tangible:
- Technical PMs can use Gemini CLI or Claude Code to spin up scripts, wire APIs, and test logic.
- Non-technical PMs can use tools like v0, Replit, or Lovable to create clickable demos.
The goal isn’t polish- it’s momentum.
2. Explore Alternatives, Not Just Solutions Great PMs thrive in ambiguity. With AI, you can now ask for multiple approaches upfront:
"Give me three ways to solve this flow, one optimized for speed, one for personalization, one for simplicity. Compare the trade-offs."This reframes the PM role from spec-writer to option-shaper.
3. Prompt Like a Builder Your prompt is the new spec. A good one frames the user problem, context, and constraints clearly. Treat prompts as artifacts you refine, version, and improve- just like product docs.
4. Ship Small, Ship Safe Push incremental value without stepping on engineering’s toes: copy changes, analytics tweaks, config updates, feature-flagged experiments. Done transparently, this strengthens trust and shortens feedback loops.
Technical PMs Have an Edge
AI has raised the floor for all PMs. Non-technical PMs can now do more than ever before. But PMs with engineering backgrounds still have a higher ceiling. They can push AI deeper, validate architectures, and bridge conversations with authority.
That edge matters. But so does curiosity. Any PM willing to experiment, prompt thoughtfully, and ship responsibly can evolve their craft.
Looking Ahead
The implications ripple outward. Product-minded engineers are already on the path to becoming technical PMs, combining system fluency with user empathy. And PMs who embrace their builder persona will become more credible, more collaborative, and more effective leaders.
This isn’t about becoming more productive. It’s about becoming more craft-driven.
The PM craft is shifting: from writing docs to creating prototypes, from handing off ideas to shaping them, from being facilitators to being builders.
The best PMs of the next decade won’t measure their value in Jira tickets closed or documents shipped. They’ll measure it in how quickly they can move an idea from concept to something you can click, test, and refine.
This is the builder moment for PMs. The question is: how will you evolve your craft?