I want PMs to vibe code. I mean it. Learning to build with Claude Code is the highest-leverage skill a product manager can add right now, and the PMs who have it operate at a level the ones who do not cannot match. This is not a cautious take about staying in your lane. It is a take about which lane. The same tool that makes a PM dangerous in the good way makes them dangerous in the bad way, and the difference is entirely about where you point it.
The green zone
Vibe coding is building by describing what you want and iterating on what the AI produces. Its core property, the thing that makes it magic and the thing that makes it risky, is that it optimizes for output that looks right and produces a reaction. For a huge category of work, looking right and working well enough is the whole job. That category is internal tools and prototypes: a dashboard that pulls your product metrics into one view, a script that clusters a thousand pieces of feedback so you can see the themes, a prototype that puts a real interaction in front of five users. If any of these break, you lose an hour of your own time. Nobody's data is exposed. This is where a PM who can build is a genuine superpower, and the missing production rigor is simply irrelevant.
The red zone
Now flip the blast radius. A customer-facing feature is the opposite of forgiving. The worst case is a security hole, a data-loss bug, an edge case that corrupts something real, and a maintenance burden that lands on engineers who did not write the code and now own it forever. Here is the part that makes it specifically a PM problem: vibe-coded code optimizes for looking right, and a PM, by definition, usually cannot read the code well enough to know whether it is actually right. The exact skill gap that makes vibe coding feel magical is the one that makes shipping it to customers reckless. And the incentives are ugly, because the PM gets the speed and the credit while engineering inherits the on-call pages and the rewrite.
Prototype is not a synonym for product
The trap that catches good teams is promotion by inertia. A PM vibe codes a convincing prototype, it works in the demo, everyone is excited, and someone asks the obvious-sounding question: why rebuild it, can we just ship this? That question is where prototypes go to become incidents. The fact that a prototype already runs is not evidence it is ready. It is the bait. The division of labor that works: the PM vibe codes the prototype that proves the idea and doubles as the de facto spec, then engineers build the production version with the security, testing, and maintainability a customer feature requires.
Pick one thing to try this week: build the dashboard you have wanted for a year, or the feedback-clustering tool, and keep it strictly in the green zone where the worst case is a wasted afternoon.