You can feel that a text or a decision isn't right yet, without being able to say why. That's where AI actually earns its place: it turns a vague unease into concrete handles — a blind spot, a fragile assumption, an objection you never addressed. The questions that get you tension instead of output, and why this makes human judgment more important, not less.
Hiring a PO to keep the backlog and sit between the business and the developers? You're optimizing a circuit that is already obsolete. This piece takes apart the split between those who think the product and those who execute it: why it degrades quality, why a backlog cannot ground a profession, and why AI removes the last excuse for living with it.
AI raises the capacity to produce — not the capacity to decide. Developers move up toward product, PMs move down toward construction. This shift blurs roles without dissolving responsibilities. A full account of what AI commoditizes in product management, what remains hard, and a catalog of emerging roles with their real risks.
Four days building a real product with Claude Code — 180 commits, from scratch. What it reveals: the intoxicating speed, the traps AI creates on its own, what tests change when you're not writing the code yourself, and how far a PM can go without leaving their lane. A field report, not a doctrine.
Shipping code faster doesn't help if nobody understands what got built. AI automates exactly the tasks that used to train junior developers, and a delayed error stops teaching anything once the system has grown too complex. A few concrete anchors for staying in control: clear contracts between APIs, tests tied to actual behavior, rebuildability as a quality bar instead of raw delivery speed.
Do you lose half an hour spinning up a test environment just to answer a product question on Slack? That hidden cost disappears when AI queries the source code, the real truth of how the product behaves. Answers grounded in evidence — functions, tests, commits — instead of stale documentation. Provided the code already speaks the language of the business.
Documentation never keeps up with the code. We know it, we accept it, and yet it costs us time with every change. AI shifts the equation: when the code is clean, it becomes the source of truth from which the other artifacts—specs, changelogs, support documentation—can be regenerated. This code-centric approach demands a minimum of technical literacy, but it opens a real lever for the product managers who master it.
Your days as a PM are devoured by tasks that have nothing strategic about them. In eight days on Claude Code, I automated my competitive intelligence — gathering, organizing, updating. Time reclaimed to analyze, understand, decide. This field report shows concretely why the center of gravity of the Product Manager job is shifting: fewer intermediate artifacts, more real strategy.