Agile changed the choreography of delivery, but it did not fundamentally change the cast. We kept the same job titles, the same swim lanes, and mostly the same power dynamics. AI is different because it collapses the distance between intent and execution. Engineers can prototype in hours. Designers can ship interactive flows without waiting for front-end availability. Researchers can summarize themes across hundreds of interviews in minutes. Documentation is no longer a sacred artifact because it can be generated on demand.
When everyone can “do the thing” faster, the old product manager value proposition gets exposed.
Not because PMs are unnecessary, but because too many PMs have been operating as human middleware. In an AI-enabled team, middleware becomes friction.
Product management is becoming the bottleneck again, but not for the reason people think
Andrew Ng has been blunt about what he is seeing: engineering velocity is exploding, while product decision velocity is not keeping up. He has cited teams floating extreme staffing ratios like “1 PM to 0.5 engineers,” precisely because the constraint is no longer “can we build it,” it is “what should we build next, and why.” (The Washington Post)
That lands uncomfortably because it cuts through a decade of agile mythology. We convinced ourselves that tighter cycles and better rituals would make decisions faster. In practice, many teams just shipped smaller batches of indecision.
AI does not fix that. AI amplifies it.
If your org cannot make crisp calls on tradeoffs, positioning, risk, and sequencing, then AI turns your product into a slot machine. Lots of output, unpredictable outcomes.
The real shift: from writing requirements to engineering decisions
In AI-enabled teams, the PM’s center of gravity moves away from “capturing what we know” and toward “creating the conditions to learn faster than competitors.”
That is why the most valuable PMs are becoming:
- System designers of feedback loops.
If engineers can build ten prototypes this week, your job is to ensure you can get ten rounds of real feedback this week. Not opinions from internal stakeholders. Not a survey that takes a month. Actual behavioral signal, usability signal, and commercial signal. Ng’s point about product work becoming the bottleneck is basically a warning that many teams still run discovery like it is 2015. (LinkedIn) - Narrative owners who reduce ambiguity.
AI makes it cheap to create options. It does not make it cheap to align a company. The PM’s job is to create a shared narrative that makes tradeoffs obvious. What are we optimizing for this quarter. What risks are acceptable. What customer segment wins. What we are explicitly not doing. - Outcome executives, not ticket shepherds.
There is a reason the “PM as project manager” instinct feels so suffocating in modern teams. Dr. Bart Jaworski’s micromanagement critique hits because it describes a PM role that has quietly metastasized into dependency chasing and task decomposition, which is exactly the work AI will commoditize first. (LinkedIn)
Here is the uncomfortable truth: if your calendar is full of status checks, you are not leading product. You are compensating for a system that does not trust itself.
AI pushes PMs into an accountability gap, and you either own it or get sidelined
A lot of leaders are responding to AI by demanding “builder ratios,” fewer coordinators, more doers. You can see the cultural momentum in how companies publicly talk about AI expectations. Shopify’s CEO memo, widely circulated, framed AI usage as a baseline expectation and pushed teams to try AI before asking for more headcount. (Business Insider) Duolingo’s “AI-first” shift, including changes to how work is staffed, is another example of leadership trying to rewire the org around automation and leverage. (The Verge)
The implication is not “PMs are dead.”
The implication is: the org has less patience for roles that cannot directly accelerate learning and outcomes.
This is why the PM job splits into two archetypes in AI-enabled environments:
- The “product operator” PM who runs ceremonies, writes tickets, and translates between functions. AI eats a meaningful chunk of this, and orgs will push it into tooling, into the team, or into program management.
- The “product strategist and experiment leader” PM who sets direction, clarifies the bet, instruments the system, and drives rapid iteration with tight customer loops. This PM becomes more valuable, not less.
Most PMs want to believe they are the second archetype. Their calendars often reveal they are the first.
“But everyone can prototype now.” Exactly. That is why the PM must level up.
The PM in an AI-enabled team cannot be purely a non-technical coordinator. You do not need to be a production engineer, but you must be able to move at the speed of prototypes. Otherwise, you become the pacing item that Andrew Ng is warning about.
This is where “vibe coding” becomes a useful cultural signal. Andrej Karpathy’s framing captured what many teams are living: people can increasingly build by intent, using natural language to drive code generation. (on X)
If you are a PM and your superpower is writing a spec that takes two weeks to socialize, you will lose credibility in a world where a teammate can generate three working prototypes before your PRD is approved.
So what replaces the PRD as the PM’s leverage?
A tighter operating system for decisions.
What the best PMs are doing differently right now
They are not micromanaging delivery. They are not disappearing into strategy decks either. They are building a product learning engine that can keep pace with AI-accelerated execution.
Practically, that looks like this:
- They treat prototypes as questions, not solutions. Each prototype exists to answer one uncertainty: desirability, usability, feasibility, viability, compliance risk, adoption friction. If your prototype is not tied to a question, it is just expensive entertainment.
- They shorten the loop from build to signal. They ship behind flags, use concierge tests, run internal dogfooding with instrumentation, and put customers in front of flows weekly, not quarterly.
- They operationalize customer truth. AI can summarize interviews, but it cannot decide what matters. The PM owns the mechanism that converts messy qualitative input into clear product calls.
- They create decision hygiene. In high-velocity teams, the cost of a bad decision is not the decision. The cost is the cascade. PMs need lightweight decision records, explicit tradeoffs, and crisp “reversibility” framing so teams can move fast without becoming reckless.
- They make the team safer to move quickly. That includes guardrails for privacy, security, and compliance, especially when AI features touch regulated data. The PM is often the person who ensures “fast” does not become “fragile.”
The paradox: PMs must stop being the bottleneck by doing more “product,” not more “process”
If product management is becoming the bottleneck, the fix is not hiring more PMs to write more documents. It is upgrading the PM role into a higher-leverage function.
This is where the comparison to agile is useful. Agile gave us faster cycles, but many companies never built true empowerment. They created rituals around a command-and-control core.
AI will punish that model.
Because AI does not just increase speed. It increases optionality. And optionality without empowered decision-making becomes chaos.
So the question is not “what is the PM’s role in an AI-enabled team.”
The question is: can your PM function produce clarity, priority, and validated learning as fast as your engineers can produce code?
bencoding 