Problems, not solutions

Yes. This is like getting a bug report on an app - you don't want to hear what the user thinks the solution to their problem is, you want to hear what the problem is, so that you can look at it and relate it to other problems, consider the implications of each solution, and finally come up with a solution that might solve several problems, without causing any more elsewhere. Coming up with possible solutions without understanding the problem properly is too easy.