Hi John, thanks for your feedback. I understand that it's easy to view product and development as separate entities, but that carries some additional problems.

I agree that Product Managers should find the problems, evaluate and filter them, and then let the engineers ideate how to satisfy the requirements. But, there are several problems when you separate development from the final user.

I will not focus on any of those problems particularly, but, as a summary, I would say that you will risk getting exactly what you asked for, not what you wanted nor what you needed. That's like the old tale of the monkey's paw or the saying "be careful what you wish for." Additionally, the developers are the only ones that know exactly all the product features; maybe Product people have asked them, but only developers know exactly what is implemented and what it will do. So, somehow, they know more about the product than the Product Manager; and, if that knowledge differs, things can go wrong very quickly.