Show, don't tell.
No, AI isn't making product management obsolete. It handed me what the job always needed and never had: a cheap way to show instead of tell.
§ 01 · The question everyone asks
Everyone keeps asking me some version of the same question. Is AI making the product management job obsolete?
No.
I'll give the longer answer, because the short one annoys people. The job is not obsolete because the job was never the part AI is good at. AI writes the deck. It does not decide the deck was the wrong thing to build. Somebody still has to find the problem worth solving, figure out a way to solve it, and get a room full of people who disagree to actually work together on it. That has always been the job. It still is.
§ 02 · What the job actually is
Kai McConnell put it best. The whole job of a product manager, she told me once, is to create shared understanding among the people trying to solve a problem together. Not the spec. Not the roadmap. Not the standup. Just the picture in everyone's head, and whether it's actually the same one. I've repeated that line to more people than I can count, usually as if it were my own. (Sorry, Kai.)
Strip the job down and you get three things: finding the problems and opportunities worth chasing, working out how to solve them, and getting everyone working on them to share an understanding of what "done" looks like. None of that is producing artifacts. It's all judgment, and judgment is the part the tools don't have. AI does not find the problem. It does not know which opportunity is real. It cannot tell you that the room only thinks it agrees.
What AI changed is not the job. It's how I do the third part.
§ 03 · The way I used to do it
For years my answer to shared understanding was telling. The way to do it was to create a deck, write a brief, and tell people in meetings. I was good at all three. Crisp PRDs, tidy acceptance criteria, the occasional diagram I was far too pleased with. The documents were excellent. The understanding was not.
Here's the problem with words. When I describe a flow, I've finished the job in my own head. The reader hasn't started. They take my sentences and rebuild a version of the thing inside their own assumptions, and no two people rebuild the same one. Engineering pictures one product. Design pictures another. The exec pictures a third, usually with a chart in it. Everyone nods. Everyone leaves the room confident. Everyone is confident about something different.
Telling optimizes for the speaker. Showing optimizes for everyone else.
§ 04 · Why I kept telling anyway
Every PM knows this. The reason we kept telling anyway is that showing was expensive. To show, you needed a working thing, and a working thing needed engineers and a sprint and a build, so you couldn't spend it on a maybe. Telling was free. So we told, and we held our breath, and we found out at the demo whether the picture in the room had ever matched the one in our heads.
That math is gone now.
The thing AI tools actually changed for me is not speed of writing. It's that the cost of showing collapsed to roughly the cost of telling. I can stand up a clickable prototype in an afternoon. I can build a rough working version of an agent and put it in front of people, who then stop arguing about the abstract noun "agent" and start arguing about the actual thing doing the actual thing, which is the only argument worth having.
So I stopped writing the paragraph about how the onboarding should feel and built the onboarding. I stopped pitching the feature in a meeting and put a working version in front of people instead. The artifact becomes the center of the table. Nobody has to reconstruct anything, because it's right there, behaving. Disagreement gets specific immediately. "I don't like it" turns into "this step is wrong," which is progress you cannot buy with a deck.
The deliverable was never the document. It was never the prototype either. The deliverable has always been the shared picture, and everything else, the spec, the deck, the working demo, is only the means to it. I spent years mistaking the means for the work.
§ 05 · So, obsolete?
The opposite. AI took the cheapest, worst medium I had for the hardest part of the job and swapped in the best one. It did not take the job. It removed my excuse for doing it badly. If the room leaves with three different pictures now, that's on me, not the tools.
The job was always shared understanding. The medium was a compromise I made because the better one was out of reach. It isn't out of reach anymore. So I show. I don't tell.
Mostly.