[wittyphrasehere]

The designer should have received all relevant context prior to starting the task. There will be exceptions, where a piece of context is missed, and in these cases where feedback is necessary the format of the feedback is important.

Rather than, "do it this way because businessReasons."

Instead, try, "We must not have properly conveyed this aspect of our business, here is the relevant context. Knowing this, how do we solve this design problem?"

If the designer is incapable of translating business requirements into design solutions then perhaps they're not a product/ux designer, maybe just a visual/graphic designer.

[michaelbuddy]

"there will be exceptions"

Yes like every project that gets designed.

Start thinking real world. Feedback comes from everywhere. A website for example can represent every aspect of a company and stakeholders who will view the early phases, either for suggestions or out of team respect will provide feedback. Doesn't mean a designer responds, but sometimes they have to suck it up and change it, even when they don't think it's better.

And stop talking like just because UX is in front of a title gives somebody special power. It doesn't. Work with a few of them and you'll realize it.

[roh26it]

Often times, designers have to get feedback from the business guys because we do have a tendency to go with the flow. Especially if its not a full time job.

[wittyphrasehere]

Absolutely, feedback is just more input for finding the right solution, and is valuable from any source.

[michaelbuddy]

Except you said earlier

"just as long as there's a verification process to ensure that only designers are giving design feedback"

You can't have it both ways.