Most bad design feedback is not given in bad faith — it is given without a method. The client knows something is off but describes the wrong thing, or fixates on a detail while the real problem sits elsewhere. Learning to give feedback on a design well is a skill, and it is one that saves everyone rounds of frustration.
Start with the goal, not the pixels
The most useful feedback connects back to the objective. Before you react to a colour or a font, ask whether the design achieves what it is for. 'This does not feel trustworthy enough for a finance brand' is far more actionable than 'I do not like the blue', because it tells the designer what to solve rather than dictating how to solve it.
Be specific and point to the exact spot
General feedback produces general revisions. 'The header feels cluttered' leaves the designer guessing; a comment pinned to the exact element that feels cluttered removes the guesswork entirely. This is where commenting directly on the design beats describing it in an email — the feedback lands where it applies, and nothing gets misinterpreted.
Separate opinion from requirement
Designers need to know which notes are mandatory and which are preferences. 'The logo must be bigger for legal reasons' is a requirement; 'I think I might prefer it warmer' is an opinion open to discussion. Flagging which is which lets the designer prioritise correctly instead of treating every note as an order.
Consolidate before you send
The fastest way to derail a project is to send feedback in a trickle as each thought occurs, or to forward conflicting notes from three colleagues unedited. Gather all the feedback for a round, resolve internal disagreements first, and send one consolidated set. A shared review tool makes this easy because everyone comments in the same place and sees each other's notes.
“The single most useful habit in design feedback: point at the exact spot instead of describing it. A comment pinned to the element removes every chance of misinterpretation.”
Better design feedback in five habits
- Tie every note back to the goal, not personal taste
- Pin comments to the exact element, do not describe it in prose
- Label each note as a requirement or a preference
- Consolidate all feedback into one round before sending
- Resolve internal disagreements before they reach the designer
Frequently asked questions
How do I give feedback on a design without being rude?
Focus on the goal, not the person: explain what the design needs to achieve and where it falls short, rather than saying you dislike it. Be specific, pin comments to the exact spot, and separate mandatory requirements from personal preferences.
Why do designers hate vague feedback?
Because vague feedback forces them to guess, which wastes a whole revision round. "Make it pop" or "I do not like it" gives no direction. Specific, located feedback tied to the objective lets them fix the right thing the first time.
Should I send feedback as I think of it or all at once?
All at once. Trickling notes one at a time, or forwarding conflicting feedback from several people, multiplies revision rounds. Consolidate into one agreed set per round so the designer works from a single clear brief.
Related resources
FileFeedback
Struggling with client feedback on your projects?
FileFeedback lets clients leave frame-accurate, timestamped comments directly on your videos and images — no more email chains, no more confusion about which version they mean.
Try FileFeedback free