A common rule experienced developers tend to embrace while dealing with large amounts of feedback is that "your audience is usually very good at identifying problems, but fairly terrible at proposing practical, viable solutions".
We can't provide good solutions for them because we don't fully understand their limitations. That's information they're not going to give us. We can try, but if we give solutions that sound good, but one tiny part of it is impossible to do because of some quirk of the engine, or some rule that a higher up has imposed for some reason. Then it's no good.
