My take on how AI changes product work

16.12.2025

Like all product people, I'm trying to figure out where AI takes my role and how I can keep growing my impact. Here are my thoughts and principles I try to work with. Things are moving fast so this might not be as relevant five years from now when we are all unemployed and the robots grow our food while we sit under a tree, but - let's make some assumptions.

Firstly, AI is not a replacement for talking to users, and it is not a replacement for talking to your team. These remain the two highest-value things you do. That hasn't changed. So keep getting out of the building, distill the learnings for your team, and see what they think.

Here is what has changed, and how you should adapt.

1. Velocity is the new normal

AI drastically reduces the time required for execution. Activities that used to be time-sinks are now almost instant, meaning you can do more of them:

PMs can also now write or vibe code and ship independent MVPs or experiments. _Note: Be careful here. Do not engage in "shadow-engineering" by creating sub-optimal code that your developers will eventually have to begrudgingly maintain or clean up.

2. The AI as a "Rubber Duck"

Treat AI as a thinking partner or a consultant. It is excellent for sanity checks, finding edge cases you missed, and pressure-testing your strategy.

It is not an oracle - you must be critical of its outputs. It does provides a helpful second (or 3rd, or 875th) perspective when you are stuck.

3. Your competitive edge is shifting

Writing PRDs, generating SQL queries, and general project management are becoming commodities. Being "technical" in the traditional sense is less of a differentiator than it was five years ago.

To stay relevant, focus your personal growth in two areas:

To summarize - you can do much more in the same amount of time, but you should probably do more of the same (mostly - discovery) and not replace the things you are already doing with things that are effective but are less impactful at figuring out what and why to build.


Back to homepage