“Can you make it pop?” “It needs more energy.” “I’ll know it when I see it.”
Every designer has heard these, and almost every client has said one, usually with good intentions. The problem is that none of them tell the designer what to change. So the next round is a guess, and the round after that is another one.
Better feedback isn’t harder to give. It just starts from a different place.
What makes design feedback useful?
Useful feedback tells the designer what isn’t working for the goal, not what you would do instead. A designer can solve a clear problem in several ways. A vague reaction or a ready-made fix leaves them with one narrow option, and it’s often the wrong one.
Three things make a note easy to act on:
- It points to something specific. “The headline” instead of “the top part.”
- It connects to a goal. “Our customers skim, so I’m worried this gets missed.”
- It describes the problem. “I can’t tell what to click first” instead of “make the button red.”
Why should feedback start with the goal?
Because the goal is how everyone judges the work. If you’re reviewing a homepage, the question isn’t “do I like it?” It’s “will a first-time visitor understand what we do and know what to do next?”
Before you react to a design, say the goal out loud: who it’s for and what it should help them do. Then read every note you’re about to write against it. If a note doesn’t serve the goal, it’s probably personal taste, and that’s worth knowing before you send it.
Why describe the problem and not the fix?
You know your business better than anyone. The designer knows what makes a layout work. Feedback goes best when each person stays in their lane.
Compare these:
- “Make the logo bigger.” The designer makes it bigger. Now the page feels crowded and nobody knows why.
- “The logo gets lost on the page, and people need to recognize us quickly.” The designer can adjust size, contrast, spacing or position, whatever fixes it best.
If you do have a specific idea, share it, just label it as one. “I wonder if a larger logo would help. Open to other ways to fix it.” That keeps the problem in the conversation.
How do you separate taste from facts?
Not every opinion carries the same weight, and it helps to know which kind you’re giving.
Facts can be checked against the goal or against real people: the text is hard to read, the price is hard to find, the form asks for too much.
Taste is personal: “I’m not a fan of that blue.”
Taste still matters, because you have to live with the result. But say so plainly: “This is a personal preference, so ignore it if it doesn’t serve the goal.” Designers appreciate the honesty, and it stops a one-person opinion from quietly steering the project.
When in doubt, ask someone from your actual audience. One honest reaction from a real customer is worth more than five internal guesses.
What does a good feedback note look like?
A simple structure works for almost anything:
- What I’m looking at. “The pricing section.”
- What I notice or feel. “I couldn’t tell which plan is the main one.”
- Why it matters. “Most visitors will pick quickly and leave if it’s unclear.”
You can add a suggestion at the end, but the first three lines do the real work.
How do you handle feedback from several people?
This is where projects slow down most. Five people send five different notes, some of which contradict each other, and the designer is left refereeing.
A few habits help:
- Name one decision maker. Everyone can share input, but one person decides.
- Collect notes in one place and combine them before sending.
- Resolve conflicts before the designer sees them. If two people disagree, settle it internally, using the goal.
- Review in rounds. Layout and structure first, then details like colour and spacing. Fixing spacing on a layout that is about to change is wasted work.
When should you give feedback?
Early, and in the right order. In the first round, react to the big picture: does the direction fit the goal? Don’t comment on fonts or small details yet. Those come later, once the direction is settled.
The same thing applies to timing. Reviewing while you’re rushed, or between meetings, usually produces shallow notes. Give the work a short, focused look when you can think about it, and sleep on anything that feels strong.
Quick answers
How do I give feedback if I’m not a designer? Describe what you see and how it affects the goal, not what to change. “I can’t find the contact button” is more useful than “move the button.”
What should I avoid saying? Phrases that can’t be acted on, like “make it pop,” “more modern” or “I’ll know it when I see it.” Ask yourself what you actually mean, and say that instead.
How many rounds of revisions is normal? It depends on the project and what was agreed up front. Clear goals and clear feedback usually mean fewer rounds, because each round fixes a real problem instead of guessing.
Is it okay to say I just don’t like something? Yes, as long as you say it is taste. Honest reactions help, especially when you add what you felt.
Better notes, better design
The best design work comes from a clear problem and room to solve it. Your feedback is how that happens.
If you want a process where decisions stay clear from start to finish, that’s how I run my brand and visual design projects, and it’s just as true for websites and products.