"Make it pop." "Something feels off." "Can we try the other version from before?" Every agency has a collection of these, usually told as stories about difficult clients. Here is the uncomfortable part: vague feedback is almost always a process problem wearing a client costume. The client is not trained to review design work. You are. Which means the quality of the feedback you get is mostly determined by how you ask for it.
Five changes that raise it.
1. Put the feedback on the thing itself
The worst possible channel for design feedback is the one most agencies use: email. "On the homepage, a bit below the blue section, the text about pricing" is a treasure hunt, and after two rounds of it, half the feedback is about finding the feedback.
Let clients comment directly on the live page or the design, anchored to the element they mean. The moment feedback has coordinates, an entire category of confusion disappears. No screenshots of screenshots, no "which version were you looking at", no archaeology. This is the core of what layernote does, but whatever tool you use, the principle is the filter: if the feedback cannot point at what it means, it is not ready to act on.
2. Ask about problems, not solutions
Clients volunteer solutions: make the logo bigger, change this to red, move that up. Treating those as instructions leads to designs nobody likes, including the client. The solution is one question, asked consistently: what were you trying to do when this bothered you?
"Make the logo bigger" usually decodes to "I am worried we look forgettable". That is a real problem, and a designer has better answers for it than a bigger logo. You do not need the client to learn design vocabulary. You need to translate their reaction into a problem statement before anyone opens the file.
3. Make rounds explicit, with deadlines
Open-ended review produces feedback forever. The fix is structure that everyone agrees to up front: this is round one, everything you want changed goes in this round, it closes Friday. A deadline on the review link is not hostile; it is the thing that makes the client actually sit down and look, instead of glancing at it on a phone during another meeting and sending impressions for three weeks.
Two rounds is right for most projects. The first catches direction, the second catches details. Feedback arriving after round two is a change request, and it is priced like one. Clients respect this more than you expect, because scope they can see beats scope that surprises them.
4. Track every comment to a resolution
Feedback that disappears into a void trains clients to repeat themselves louder. Every comment should have a visible state: open, in progress, resolved, or a written "we chose not to, and here is why". The last one matters most. Declining feedback with a reason builds more trust than silently ignoring it, and almost as much as implementing it.
This is also the argument for one tracked list instead of scattered channels: a list can reach zero, an inbox cannot.
5. Lower the barrier to zero
Every hurdle between the client and the review costs you feedback quality. An account to create, a tool to learn, a plugin to install: each one filters out the busy stakeholder whose opinion arrives late by email instead, after the build, when it is expensive. The review link should open in a browser and work immediately, on the page itself, no login. The client who was "too busy to look" is usually a client who hit friction on the previous round.
The pattern
All five changes are the same move: shift effort from the client to the process. Point at the thing, translate reactions into problems, bound the rounds, close every loop, remove every hurdle. Clients are not bad at feedback. They are exactly as good as the process you hand them.