How to give design feedback that designers can actually use
Seven habits that make design feedback faster to act on, with before-and-after examples of vague and useful comments.
Design reviews often go wrong in predictable ways: feedback that’s too vague to act on, feedback that dictates a solution instead of describing a problem, and feedback from several people that contradicts itself. The habits below fix most of it, whether you’re a client, a manager or a fellow designer.
1. Start from the goal
Every design has a job: get sign-ups, explain a product, make a brand feel premium. Judge the work against that job. “I don’t like green” is a preference; “the green makes the warning look like a success message” is about whether the design does its job. If there’s a creative brief, keep it open during the review.
2. Give big-picture feedback first
Comment on structure and message before colours and fonts. If a whole section needs to go, there’s no point polishing its spacing. A simple order works well: goal, message, layout, then visual details.
3. Describe the problem, not just the fix
Designers are good at solving problems, but only if they know what the problem is.
- Vague: “Make the logo bigger.”
- Useful: “On the phone mockup I didn’t notice the logo at all. Can we make the brand more visible here?”
The second comment might lead to a bigger logo, or to a better solution, like moving it or adding contrast. Both outcomes are better than a guess.
4. Point at the exact spot
“The image on the left” is ambiguous on a page with four images. Put your comment directly on the element. In a review tool like edits.io, reviewers click on the design to drop a numbered pin, so there’s no doubt what each comment refers to. If you’re working with a flat image, our free image annotator lets you add numbered pins and arrows before sending it.
5. Be specific about what you feel
“It doesn’t pop” is hard to act on. Try to name the reaction: “I’m not sure where to look first,” “the text feels hard to read over the photo,” or “this looks more playful than our other materials.” Those point the designer towards hierarchy, contrast or tone.
6. Prioritise
Label comments so the designer knows what matters:
- Must change: errors, brand or legal problems, anything that stops the design doing its job.
- Should change: things that weaken it.
- Consider: ideas and preferences.
7. Consolidate before sending
When several people review, contradictions are inevitable: one person wants more white space, another wants more content above the fold. Ask everyone to comment in one shared place so they can see each other’s notes, and agree who makes the final call.
Examples: vague vs useful
| Vague | Useful |
|---|---|
| Can it be more modern? | The drop shadows and gradients feel dated next to our new website. Could we try flatter cards? |
| The text is wrong. | The headline says “from $9”, but the cheapest plan is $12. |
| Too busy. | There are three different call-to-action buttons in the hero. Which one matters most? |
| Fix the photo. | The product is cut off at the right edge on the mobile version. |
A checklist to keep you on track
Our design feedback checklist walks through goal, message, layout, brand, imagery, accessibility and final details. Copy it into your next review.
Summary
- Judge the design against its goal.
- Big picture first, details last.
- Describe the problem, point at the spot, and explain the reaction.
- Prioritise, and keep everyone’s feedback in one place.
Collecting design feedback from clients? Try edits.io free. Reviewers click on the design to comment, no account needed.