How my life as a PM is changing with AI
I have a confession to make: I wasn’t an early adopter of AI. I did not dive headfirst into this new technology, aggressively look for ways to improve my life and work, or start a YouTube channel.
Instead, I approached the topic slowly, with curiosity but without FOMO. Over time, I explored different capabilities and tools, from ChatGPT to n8n, from helping me draft documents to automating recipes on my self-hosted recipe book (yes, I’m that kind of person!).
But in 2025, I decided to focus my efforts on using different tools to make my life as a Product Manager easier and more efficient. I was lucky that my company decided to provide us with Gemini first and Claude second, and the combination of Google’s Workspace and Claude Code turned out to be an absolute beast.
Here are a few highlights of how my work has changed, along with some personal reflections.
From Product Manager to Product Builder
This is definitely one of the biggest improvements, and it deserves the first mention. By integrating AI into my professional life, I was able to move from idea to customer testing in 90% less time.
Before AI, it would take a considerable amount of time to turn an intuition, an idea, or a sketch on my iPad into something I could show to stakeholders - including actual customers - to get early validation.
Don’t get me wrong: it was a lot of fun building interactions with InVision, Sketch, and Figma, but the time and design help needed made the process so slow that some features just weren’t worth testing at all.
Nowadays, I can turn an idea into a testable prototype in a single day. And it’s not just clickable screens: I can code a real app, hook it up to exports from our data lake, and let a user test it with their own data!
This is how many PMs are now entering the era of Product Builders: all that is needed is a clear vision, a well-prompted thinking agent, a designer agent, and an engineer agent working together - no more technical ceiling separating ideas from actual working products.
Gathering information is a (dangerous) breeze
One of my biggest personal projects in 2026 was to create an “information aggregator” that would combine all the different sources I navigate on a daily basis into a single, well-organized dashboard. I’m talking ProductBoard insights, Slack threads, meeting notes, emails, customer interviews, competitive intelligence signals…
LLMs are incredibly good at these sorts of tasks, which means I was able to create such an aggregator without too many technical issues. As a result, I wake up in the morning and need only a few minutes to get up to speed on all my projects and areas of expertise across a dozen different sources.
However, I am extra-careful about avoiding information overload. If you let everything that is potentially interesting to you into your personal knowledge database - or second brain - it will be bloated in no time, making it impossible to distinguish what is worth exploring further from what should stay in the mind’s backlog. And obviously, let’s always keep an eye out for hallucinations!
That’s why I’m always skeptical when I read articles on Substack by PMs claiming their entire workflow is on autopilot and they have little to no work to do. On my end, even if I put my ship on autopilot, I still spend most of my days talking with the crew, connecting with passengers, aligning with engineers, and looking at the ocean to spot icebergs.
You are still a Product leader
There is no such thing as a free lunch. Because AI execution is remarkably cheap, product strategy must become significantly sharper and tighter.
Let me be clear about something: customers don’t care that I can vibe code something for them in a day; they don’t care that I have a polished dashboard where all their feedback is fed to me while I sip my morning coffee. All they care about is whether my product is something they want to pay for because it solves their problems and makes their lives easier.
And when any team can build - and test - functional interfaces in hours, what seems to be a fast lane toward product improvement may very easily turn into organizational chaos.
So, at any given moment, I want my team and I to be 100% aligned on the vision, the strategy, and why we are building - or not building - that one thing right now. Specifically, I always make sure that everybody can instantly answer these three questions:
- What concrete customer pain are we fixing, and why right now?
- What gives our product an uncopyable edge over rivals?
- What are we deliberately choosing NOT to build?
To begin with, this helps me avoid tunnel vision. When everybody is on the same page, they can spot that the team is on the wrong page sooner than I would on my own.
Moreover, as Arthur C. Brooks points out in his book The Happiness Files: Insights on Work and Life, sharing the big picture is a core requirement for human happiness and motivation. When my teammates explicitly understand the why behind what we choose to build - and what we choose to reject - their work is no longer just a checklist of cheap code. Instead, it becomes an exercise in earned success and genuine service to the customer.
Finally, and this is often an underestimated point, it drastically cuts down on misunderstandings with other teams. I’ve lost count of how many times someone working with me on a project has spoken with another team, and their inability to clearly explain what we were building and why has raised a million red flags that I then had to address with executives out of nowhere. That’s why I’m now extra careful to make sure everybody fully understands this idea before anybody touches a line of code.