Microsoft's CPO said prototypes replace PRDs. This is wrong in a specific way. Prototypes capture user experience and functional requirements. They show what the product does. They don't capture why you're building it. How does this feature differentiate from competition? How will you acquire users for it? How does it improve monetization? What's your hypothesis? What metrics define success? A prototype can't answer any of these questions. And teams that ship prototypes without strategy are just building faster in the wrong direction. The actual unit of work for a PM now is prototype + PRD. Remove the experience details from the PRD since the prototype handles those. Keep the strategic reasoning. Shipping faster without strategic clarity is just failing faster.