Customer-centric product development is treated as self-evidently correct. Gather data, listen to users, build what they ask for. The logic seems airtight. The historical record is more complicated.
What customers consistently get wrong
Customers describe problems accurately but propose solutions poorly. They anchor to what already exists, underestimate what they would adapt to, and cannot reliably predict their own behaviour in conditions they have never experienced. Systematic customer feedback collection codifies the present rather than anticipating what becomes valuable next.
The argument for listening closely
Customer feedback surfaces real friction points, identifies service failures, and validates whether a feature addresses an actual need rather than an assumed one. These are legitimate uses. A business ignoring direct customer input entirely is making a different kind of error.
The argument for skepticism
Henry Ford's alleged comment about faster horses is a cliche, but the underlying observation survives scrutiny. Focus groups consistently rated early streaming interfaces as confusing and unappealing. Survey respondents said they preferred physical media. The companies that listened to those signals and stopped developing digital distribution made poor long-term decisions.
Customer feedback tells you where your current product is failing. It rarely tells you what your next product should be.
Businesses that treat feedback as directional input — one signal among several — tend to make better innovation decisions than those who treat it as a mandate. The distinction matters more than most strategy documents acknowledge.