Customers should inform you about problems they need solving, not how the problem will be solved by your software. It is your job to propose solutions (and this is often best done with a super simple prototype, not even in real software). They can feed back on your solution and it might be that 10% of users love your solution but there is a better solution out there for 90% of users. Implement the simplest of them and see if users want to use them.

When people can't even make features that make sense to users, generating ideas to go in the backlog is a terrible idea.

If you want to understand your users problems and how your product addresses them properly I cannot recommend the book Mental Models by Indi Young enough: https://www.amazon.com/Mental-Models-Aligning-Strategy-Behav...

The nice thing about mental models is you have so many to choose from[1][2][3][4][5][6][7][8].

[1] https://medium.com/@yegg/mental-models-i-find-repeatedly-use...

[2] http://www.defmacro.org/2016/12/22/models.html

[3] https://fs.blog/mental-models/

[4] https://nesslabs.com/mental-models

[5] https://amzn.to/2KiKQEg (Don't recommend)

[6] https://amzn.to/2GOHoz4 (written by DuckDuckGo founder Gabe Weinberg)

[7] https://amzn.to/31lfK4Q (A classic)

[8] https://amzn.to/31tX17l (Haven't read but recommended by others)