I'm not arguing that Product should sit high and mighty and refuse to listen to Development. Great ideas can come from everywhere, including Development, of course. But understanding what ought to be built, at least for functional requirements, is fundamentally Product's job and their decision.

What great teams do is that they have a Product guy sit on the same team as Developer guy(s), precisely to avoid the malaise you describe.