That's the difference between having features people use, and having features people think they will be used - communication. Often times customers come with f

That's the difference between having features people use, and having features people think they will be used - communication. Often times customers come with feature requests but dev/biz fail to translate that into problem resolutions. "I want it to export all my data for this time period", should be followed by an in depth discussion on why that's needed, whose going to do perform the task, how often, under which circumstances. A bad translation more often than not translates to bad UIs, half-features, and hours upon hours wasted on dev time and customer support time.