[skybrian]

"Requirements" is an often-misleading word. The danger is putting the customers on a pedestal while at the same time not really listening or understanding.

Supposed "requirements" are sometimes merely design preferences. Customers will often trade them for other things they want more (time to delivery, higher priority features, alternative implementations) if given a chance. Unless you have a good relationship with the customer so you can negotiate these tradeoffs, you may build something that meets requirements but isn't what they really want.