How to Give Good Design Feedback (A Guide to Share With Clients)
Vague notes like 'make it pop' stall design projects. A practical guide to giving clear, specific design feedback, written to hand straight to your clients.
Most bad design feedback does not come from bad taste. It comes from people who know exactly how they feel about a design and have never been taught how to say it in a way a designer can use. "Make it pop." "I don't love it." "Can it feel more premium." The reaction is real. It is just not yet feedback anyone can act on.
If you are a designer, this piece is written so you can send it to your clients at the start of a project. If you are a client who was handed this link, welcome. You were given it because your designer wants to get your revisions right on the first try, and clear feedback from you is how that happens. Either way, the goal is the same: turn the feeling you have about a design into something specific enough to change.
Why vague feedback costs everyone time
When you tell a designer "the header feels off," you know precisely what you mean. You can see it. But the designer receiving that note cannot see your reaction. They can only see your words, and "off" points in a hundred directions. Too big? Wrong color? Crowding the logo? Bad font?
So the designer guesses. They pick the most likely interpretation, make a change, and send it back. If they guessed right, great. If they guessed wrong, you have both burned a revision round on a misunderstanding, and the thing that actually bothered you is still there. Multiply that across a project and a two-week job becomes a month, not because anyone did anything wrong, but because the feedback never carried enough information to act on the first time.
Specific feedback is not about being demanding or knowing design jargon. It is about giving the designer enough to work with that they do not have to read your mind.
Say what, where, and why
The most useful piece of advice fits in one line: for each note, try to cover what you are reacting to, where it is, and why it bothers you.
What and where locate the problem. Instead of "the top feels cluttered," try "the three icons directly under the logo feel crammed together." Now the designer knows the exact element, not a general zone.
Why is the part clients most often skip, and it is the most valuable. "Move the button up" tells the designer what to do. "The button is below the fold on my laptop, so I worry people won't see it" tells them the actual problem, and a good designer might solve that better than moving the button, by changing the layout so the button rises naturally. When you give the reason instead of only the fix, you let the person you hired for their judgment actually use it.
A quick before-and-after:
- Instead of "make it pop," try "the headline doesn't grab me the way our storefront sign does. It feels quieter than our brand usually is."
- Instead of "I don't like the colors," try "the blue feels colder than our brand, which is supposed to feel warm and friendly."
- Instead of "it looks cheap," try "the thin font on the logo reads less premium than I'd like for a product at our price point."
None of those require design vocabulary. They just describe the reaction and its reason in plain language, which is all a designer needs.
Separate the problem from the solution
Clients often jump straight to a fix: "make the logo bigger," "use a different font," "add more white space." That is a natural instinct, and sometimes the fix is right. But when you lead with a solution, you hide the problem underneath it, and the problem is what the designer actually needs.
"Make the logo bigger" might really mean "I'm worried people won't know whose site this is." A bigger logo is one answer. A designer might have three better ones. But they can only find them if you tell them the worry, not just the instruction.
You do not have to stop suggesting solutions. Just try to include the problem behind them. "The logo feels small to me, and I think I'm worried it's not memorable enough" gives the designer both your instinct and the reason, and lets them steer. That is the difference between hiring someone for their expertise and using them as a pair of hands.
Consolidate before you send
One of the most helpful things a client can do has nothing to do with the content of the feedback and everything to do with its packaging: gather all of it, from everyone on your side, and send it in one pass.
Feedback that trickles in, a note today and a follow-up two days later, forces the designer to work in a start-stop rhythm and often to redo things as new notes contradict old ones. Worse is contradictory feedback from different people on your team arriving separately, leaving the designer to referee. Decide internally first. Have the disagreements on your side, reach a consolidated position, and hand over one coherent set of notes. It respects the designer's time and gets you a cleaner result.
Point at the design, not around it
Where you leave feedback matters as much as what it says. Describing a location in words, like "the header, no, the other one, near the top," is error-prone before anyone has even discussed the substance of the note.
The fix is to comment directly on the design itself, pinned to the exact spot, rather than in an email or a chat message next to a screenshot. When your note is attached to the specific element you mean, the designer never has to figure out where you are pointing. This is the whole idea behind reviewing on a tool built for it: you click the thing, you leave the note there, and the ambiguity of location is gone before you even get to the ambiguity of wording. If your designer sends you a review link instead of asking for feedback over email, this is why, and using it as intended makes your feedback markedly more useful.
Be honest, and be kind, and know they can take it
Two failure modes sit at opposite ends. Some clients soften feedback so much the designer cannot tell what they actually want. Everything is "great" until the final invoice, when it turns out nothing was. Others deliver critique like a demolition. Neither helps.
The middle is straightforward: be direct about the work, warm about the person. Designers want to get it right and would much rather hear a clear problem now than a polite non-answer that leads to a version you quietly dislike. You are not going to hurt a professional's feelings by saying the blue feels cold. You will frustrate them by saying "looks good" and then asking to change the blue three rounds later. Say the real thing, early, kindly. That is the feedback that actually helps.
A short checklist to keep handy
When you sit down to review a design, a quick pass through these will make almost any feedback more useful:
- Am I pointing at a specific element, not a general area?
- Did I say why it bothers me, not just what to change?
- Did I describe the problem, or only jump to a fix?
- Have I gathered everyone's notes into one consolidated set?
- Am I leaving the note on the design itself, where the designer can see exactly what I mean?
- Am I being honest now rather than agreeable now and unhappy later?
None of this requires design training. It just requires treating feedback as information you are handing to someone, and asking whether you have given them enough to act on.
Frequently asked questions
What is an example of good design feedback?
Good feedback names the specific element, describes the problem rather than only a fix, and explains why it matters. For example: "The call-to-action button feels easy to miss because it blends into the background, and I'm worried visitors won't spot it." That gives the designer the what, the where, and the why, so they can solve it well on the first try.
Why is "make it pop" bad feedback?
Because it describes a feeling without any information the designer can act on. "Pop" could mean brighter color, bigger type, more contrast, more white space, or a dozen other things. The designer has to guess which, and a wrong guess wastes a revision round. Saying what specifically feels flat, and why, gives them something to work with.
Should clients suggest solutions or just describe problems?
Describing the problem is more valuable, because it lets the designer apply their expertise to solve it. Suggesting a solution is fine as long as you also include the problem behind it, so the designer can either use your idea or offer a better one that addresses the same underlying concern.
How can I make my design feedback clearer to act on?
Leave your comments directly on the design, pinned to the exact spot you mean, instead of describing locations in an email. Consolidate all your notes into one set before sending, describe the problem and not just the fix, and be specific about which element you are reacting to.
Aligno lets clients pin feedback to the exact spot on a design and approve when it's right, no account needed. If you're a designer, share a review link and send this guide alongside it.