Giving the users what they want isn't a direct result of asking them what they want.
Discussion
If I had given the people what they want it would have been more horse carriages
- Henry Ford
We're currently working to build infrastructure and a platform that contains technology most users have never even heard of that does things they didn't even realize could or should be done and that they probably see no purpose in.
And we're doing that, in order to build better doo-dads for them, at some later date, including some doo-dads that would otherwise be impossible to build.
We know that they want this.
They do not know that they want this.
man, can I relate to this..
So many people ask for the solution they think they want, but can't actually define the problem they need solved. Because they also don't understand the technology, the solution they ask for is rarely the solution they need.
This is true with tech and true spiritually with our prayers.
Also true in business when working with clients. There are the perceived needs and then there are the actual needs. Sometimes they align, often the do not.
Yes, I used to do requirements engineering and the customers would often come in, annoyed at something, and tell us they want XYZ.
After talking to them, for a while, and discussing it with developers, we'd come back to the table with "How about ABC?"
They didn't even know that ABC was a thing, until we told them. Because we had to invent it.
Users typically want faster horses.