Knowing how to give design feedback can be the difference between a second draft that fits the goal and a long run of revision rounds that drain your budget. Good feedback tells a designer what is working, what is not, and why, in terms of the goal you agreed on. It does not tell them which shade of blue to use. This guide gives you a simple structure, phrasing you can copy, and a checklist for each review round.
Who this guide is for
This guide is for small business owners, studio founders and small-team leads who review work from freelance designers, agencies or an in-house creative. You do not need design vocabulary to learn how to give design feedback that is useful. You need a clear goal, a calm process and a few habits that keep comments specific.
Why design feedback goes wrong
A frustrating revision cycle can often be traced back to a handful of avoidable problems. The feedback arrives in pieces from several people. It describes personal taste rather than the project goal. Or it prescribes a fix (“make it pop”) without explaining the problem the reviewer saw. In each case the designer has to guess, and guesses cost rounds.
In her Nielsen Norman Group article on design critiques, Sarah Gibbons identifies three foundations for productive critique: a clear scope for what is and is not being reviewed, agreed objectives covering the problem, user needs and design goals, and conversation rather than commands. Those three ideas work just as well for a business owner reviewing a freelancer’s draft as they do for an internal design team.
How to give design feedback: a five-step structure
Use these steps every time you review a draft, whether it is a logo, a brochure or a website page.
1. Re-read the brief first
Before you open the file, re-read the goal, audience and key message you agreed with the designer. This keeps your comments anchored to the job rather than to your mood that day. If the brief has changed since the project started, say so up front; otherwise the designer will be judged against a target they never saw.
2. Look at the work as your customer would
View the design in the context it will live in: on a phone if it is a social post, at arm’s length if it is a flyer, from across a room if it is signage. Note your first reaction, then ask whether the intended audience would understand the message and know what to do next.
3. Start with what is working
Name the specific things that meet the goal so the designer keeps them. “The headline is easy to read from a distance” is useful. “Looks great” is not, because it does not tell the designer what to protect in the next round.
4. Describe problems, not solutions
This is the most important habit. Tell the designer what is not working and why it matters for the goal, then let them propose the fix. The NN/g article gives an example of turning a reaction such as “I love those colors, but that button is wrong” into a question tied to the objective: “If quick registration is the goal, are we emphasizing the right elements?” Questions like this invite the designer’s expertise instead of overriding it.
5. Prioritise and consolidate
Group your comments into “must change,” “should change” and “nice to have.” Then send one consolidated set of feedback from one person. If several people reviewed the work, merge their notes and resolve contradictions before anything reaches the designer.
Design feedback phrasing: what to say instead
The table below shows common reactions and a more useful way to say the same thing. Notice that each improved version names the goal or the audience.
| Instead of | Try |
|---|---|
| “I don’t like it.” | “I’m not sure this feels right for first-time customers. Can you walk me through the thinking?” |
| “Make the logo bigger.” | “People need to recognise us from the street. Is the logo doing enough at that distance?” |
| “Change the colour to green.” | “The colours feel colder than our brand. We describe ourselves as warm and friendly.” |
| “Make it pop.” | “My eye goes to the photo before the offer. The offer is what we need people to see first.” |
| “It’s too busy.” | “There are a lot of competing elements. Which one should a reader notice first?” |
| “My partner hates it.” | “A second reviewer felt the tone was too formal for our audience. Here is the specific section.” |
Running a short feedback session
For anything bigger than a single graphic, a short live session can resolve more than a long email thread. Atlassian’s Team Playbook describes a “Sparring” play for peer feedback that runs about 30 minutes with two to five people. It moves through preparation, setting the stage with goals and feedback areas, a silent review where people note strengths, suggestions and questions, a discussion of themes, and a wrap-up with next steps. The playbook also stresses focusing on the work, not the person.
A simple agenda adapted for a business owner and a designer:
- Designer presents (5 minutes). The designer restates the goal and explains key decisions. Hold questions until they finish.
- Silent review (5 to 10 minutes). Everyone notes what works, what does not, and open questions.
- Discussion (10 minutes). Go through themes, starting with what is working. Ask “why” before suggesting changes.
- Agree next steps (5 minutes). Confirm the must-change list, the owner of each item and the date for the next draft.
The NN/g article also recommends a facilitator role whose job is to keep time, keep discussion on track, reformulate vague or directive comments, and document outcomes. In a small business that may simply be you, so keep a notes document open and write down every agreed change.
Worked example: a hypothetical studio reviewing a website homepage
Imagine a three-person interior design studio reviewing the first homepage draft from a freelance web designer. The brief’s goal was “get homeowners to book a free consultation call.”
The owner’s first reaction is “it feels a bit flat.” Rather than sending that, she uses the five steps above on how to give design feedback:
- Brief check: The goal is booking calls. The audience is homeowners planning a renovation.
- Customer view: On her phone, the booking button sits below three large project photos.
- What works: The photos show the studio’s style clearly, and the navigation is short and plain.
- Problems: A visitor has to scroll past all the photos to find the booking option. The headline describes the studio but not what the visitor gets.
- Priorities: Must change: booking option visibility on mobile. Should change: headline focus. Nice to have: a short line under each photo naming the room type.
The designer now knows exactly what to protect, what to fix and what matters most, without being told how to lay out the page.
A design feedback checklist for each round
Use this list as a quick reminder of how to give design feedback each time a new draft arrives.
- I re-read the brief and goal before reviewing.
- I viewed the work in its real context and size.
- I named at least two specific things that are working.
- Each problem is described in terms of the goal or audience.
- I asked questions where I was unsure of the designer’s reasoning.
- Comments are sorted into must, should and nice to have.
- Feedback from all reviewers is merged into one message.
- I stayed within the agreed number of revision rounds, or discussed extra rounds first.
- The next draft date is confirmed.
Save this checklist with your other process documents. If you are building out repeatable workflows, our business systems articles cover how to keep templates like this easy to find.
Mistakes to avoid when giving design feedback
- Feedback by committee. Several people commenting directly to the designer creates conflicting instructions.
- Drip-feeding comments. Sending notes over several days means the designer starts work before the full picture arrives.
- Moving the goalposts. If the goal has changed, update the brief and treat it as a scope conversation, not a revision.
- Pixel-level edits too early. Commenting on spacing in a first concept distracts from whether the overall direction is right.
- Silence. Delayed feedback stalls the project and can push the designer onto other work.
Key takeaways
Good design feedback is anchored to the brief, starts with what is working, describes problems rather than prescribing fixes, and arrives as one prioritised message from one person. Use questions to understand the designer’s reasoning, run a short structured session for bigger pieces, and keep a checklist so every round follows the same process. Clearer feedback gives you the best chance of fewer rounds and work that fits the goal you set.
Written by the Design Productive Editorial desk. Disclosure: this guide contains no affiliate or sponsored links.


