A CPO at a company worth more than 16 billion dollars told his product team three things in a casual tweet: push markdown to git repos instead of building planning decks, watch customer session replays directly via MCP instead of waiting for summaries, and fix your own copy instead of filing tickets for engineers. Three bullets. No memo. No transformation initiative. The casual tone is the point. Inside companies moving fast, this already feels like Tuesday. Each of those three things strips away one layer of translation between the PM and the actual product. Strip away enough layers and the translator role just vanishes.
The fifteen-year middleware problem
Over the last fifteen years, the PM role became a weird middleman job: planning decks, PRDs in Google Docs, Jira tickets, review meetings, quarterly business reviews. Why? Because PMs could not touch the product. You could not write code, so you documented what you wanted someone else to write. You could not look at session data, so you waited for an analyst. You wanted to change a button label, so you filed a ticket and nagged the engineer. Each time you translate something, you lose information. The customer says "this is confusing." The PM writes "users report discoverability challenges with the onboarding flow." We called it being the voice of the customer. It was really telephone with PowerPoint.
Three layers collapsing at once
Layer one, the planning artifact. PMs now write where engineers write: markdown in git repos, version-controlled, next to the code it describes. Layer two, the information bottleneck. Tools like LogRocket let you query session replays in plain English via MCP. One prompt scans every session, spots rage clicks, finds broken flows. No analyst, no dashboard, no "let me set up a meeting." Layer three, the execution handoff. "Fix your own copy" sounds small. It means the PM finds the component, changes the string, pushes the PR. Multiply that across a hundred PMs and you free thousands of engineering hours previously spent on find-and-replace tickets. Strip these three layers and there is no reason for a PM to be a translator anymore.
What survives and what dies
Not all of the job is translation, and the stuff that is not becomes more valuable. Judgment gets harder when you can build anything, so the job becomes taste and conviction about what moves the dial. Customer intuition stays human, because MCP shows you users are confused but not why. Cross-functional alignment stays human, because AI cannot convince a skeptical VP in the hallway. Systems thinking stays, because touching code means knowing where things break.
What dies: the planning deck, the weekly metrics review meeting, the voice-of-customer monopoly, and the feature-factory PM whose whole day is roadmap-item-to-ticket-to-handoff. That is pure middleware and the most exposed role in the industry.
Here is the uncomfortable question to sit with this week. If your PMs can push to repos, pull production data, and prototype code, what are your twelve PMs actually doing that needs twelve people? Most orgs will find they need fewer PMs doing radically different work: part strategist, part builder, part analyst.