Simple: they’re trying to give you the solution, and it’s your duty as the responsible designer/developer to find out what problem they see. Here’s a nice set of questions I’m using (from Managing projects, people, and yourself [1] by Nick Toverovskiy):
1. What did you mean by that?
2. Why is it important?
3. How is this related to the purpose of the project?
4. How does this relate to other parts of the system? What else could be affected by this change?
5. Why is it critical to resolve this before the next release / deadline?
This should paint a fairly decent picture of what’s really on your client’s (or manager’s) mind. Then you can propose a solution to the real problem – which might very well be the one that your client has proposed!
(Some questions might sound stupid in context. You can skip them, or just admit it: “I’m gonna ask some questions which might make me sound like an idiot, but that would really help me figure out the problem better. Would that be alright with you?”)
[1]: https://bureau.ru/books/fff-demo/20 (in Russian)