Short answer
Useful design feedback starts from the brief: say whether the work meets the goal and speaks to the audience, describe what isn't working and why instead of dictating the fix, separate must-change notes from preferences, and send one consolidated list from all reviewers by an agreed date.
Key takeaways
- Review against the brief's goal, audience and message before you react to taste.
- Describe the problem ("the price is hard to find") and let the designer solve it.
- Label every note as must-fix, should-fix or a preference.
- One person gathers all reviewers' notes and resolves conflicts before they reach the designer.
Most design projects don't go wrong in the design. They go wrong in the feedback: five people send overlapping notes, two of them contradict each other, one says "make it pop," and the designer spends a round guessing. Good feedback is a skill, and it can be learned in an afternoon. This guide gives you a simple method you can use on the next round.
What should you check before giving any feedback?
Check the work against the brief first: the goal, the audience, the single message and the deliverables.
Open the brief next to the design. If you used the creative brief builder, you already have it on one page. Then ask four questions:
- Does this work toward the goal we wrote down?
- Would the audience we described understand it and care?
- Is the single message obvious within a few seconds?
- Are all the formats and sizes we listed here?
Notes that come out of these questions are the most valuable ones you will give. They are also the easiest for a designer to act on, because they point back to something everyone already agreed. If the brief itself turns out to be wrong, say so plainly and fix the brief, rather than smuggling a new goal in through feedback.
How do you describe a problem without designing it yourself?
Say what isn't working and why, and leave the solution to the designer.
"Make the logo bigger" is a solution. The problem behind it might be "people won't know who this is from," and a designer might solve that with placement, contrast or a tagline instead. A designer who knows the problem has more options than one who receives an instruction.
| Instead of this | Try this |
|---|---|
| "Make it pop." | "It blends in with the other posts in the feed; it needs to stand out at small size." |
| "Use blue." | "The red feels urgent, and this is a calm, reassuring message." |
| "Move the price up." | "People scanning this may not find the price." |
| "I don't like the photo." | "The photo shows a team, but the audience is solo freelancers." |
Factual corrections are the exception. Wrong dates, typos, legal lines and missing logos should be stated directly.
How do you separate real problems from personal taste?
Label every note as must-fix, should-fix or preference, so the designer knows what is required and what is optional.
- Must-fix: errors, legal issues, anything that breaks the brief.
- Should-fix: things that weaken the work against its goal.
- Preference: your taste. Fine to share, fine for the designer to push back on.
Ranking forces the reviewer to think about why a note matters. It also stops a small preference from getting the same weight as a wrong phone number.
How do you combine notes from several reviewers?
Have one person collect every reviewer's notes, remove duplicates, settle contradictions and send a single list.
Designers should never receive two emails that say opposite things. The person who owns the project, usually whoever is named as the approver in the brief, gathers notes by a set deadline. Where reviewers disagree, that person decides, or goes back to the brief to break the tie. Number the notes and attach them to the file, ideally as comments pinned to the exact spot on the design.
What does a good feedback note look like?
A good note names the spot, describes the problem, links it to the brief and states its priority, all in one or two sentences.
Here is the same reaction written two ways.
Weak: "Not sure about the header. Can we try something else?"
Useful: "3. Header (must-fix): the headline says 'Book now,' but the brief's goal is newsletter sign-ups. The call to action should point to the sign-up, and the booking message can move to the email."
The second version tells the designer where to look, what is wrong, why it matters and how urgent it is. It takes ten seconds longer to write and saves a round. If you find you can't fill in the "why" part, that's a sign the note may be a preference, and it should be labeled as one. A quick test before sending: could someone who wasn't in the room act on this note without asking you a question?
How should feedback be delivered?
Deliver it in writing, numbered and specific, with a short live conversation for anything complex.
Written notes give the designer something to work through and tick off. A 15-minute call on top of that is worth it when the direction is changing or the notes are subtle. Start with what is working. That is useful information in its own right, because it tells the designer what to keep while they change the rest. Nielsen Norman Group's guidance on design critiques makes the same point about agreeing on goals up front and keeping the discussion about the work, not the person.
When should you stop giving feedback?
Stop when the work meets the brief, all must-fix notes are resolved, and further rounds would only change preferences.
Endless polishing costs money and morale. Before each round, ask whether the remaining notes would change the result for the audience. If they would not, approve the work, note the preferences for next time and launch. A plan with a fixed number of rounds, written into the brief and the schedule, makes this decision easier for everyone. Our guide on planning a creative production shows how to fit review rounds into a realistic timeline.
Questions
How many rounds of design feedback are normal?
Two or three rounds is a common plan for small projects: one on concepts, one on the chosen direction and a final round for corrections. Write the number into the brief or contract so everyone knows extra rounds have a cost.
Should I tell the designer exactly what to change?
Only for factual fixes such as a wrong date, a typo or a missing logo. For anything about layout, color or hierarchy, describe the problem and the goal, then let the designer propose the solution. That usually produces a better result.
What if I just don't like it?
Try to say why in terms of the brief. "It feels too formal for an audience of first-time customers" is something a designer can work with. If you can't connect the reaction to the goal or audience, mark it as a preference.
How quickly should feedback come back?
Agree on a turnaround when you plan the schedule, often one to three working days per round on small projects. Late feedback squeezes design time later, which is where quality suffers.