What makes design feedback examples clear
A design feedback example shows the same comment written two ways, vague and clear: for example, “Can you make it pop more?” becomes “The Book a table button gets lost next to the photo; can it stand out more, so it is the first thing people see?”, which tells the designer what to change and why.
Most review rounds that go wrong start with a comment that sounded clear to the person who wrote it. The examples here come in two sets. The first is feedback from clients, which you can share as a short guide before the first round. The second is what you write back to a client: confirming, asking, pushing back and asking for approval. Filter by topic or search for a word, then copy what you need.
- Location
- Where the comment applies: the page, the section, the element, and the screen size if it matters. “The logo in the desktop header” is a location; “the logo” is not, because it might mean every page, every size and every file.
- Problem before fix
- Saying what is wrong, or how something should feel, before suggesting a solution. “The prices are hard to find” lets the designer pick the best fix. “Make the prices red” locks in one fix that may not solve it.
- Reason
- A short “because” after the request: “because most buyers ask about reviews first”. A reason lets the designer apply the same rule elsewhere, and it makes push-back easier to discuss.
- Keep list
- Praise that names what is working, such as “the checkout page is exactly right, keep that style”. It protects the good parts from being changed in a later round.
- One voice
- All comments from the client’s side sent together by one person, with disagreements already settled. It is the single biggest thing a client can do to cut the number of rounds.
- Confirming reply
- Your numbered summary of what you will change, sent before you start. It turns a loose email into a list both sides agreed to, and catches misunderstandings early.
Design feedback examples, vague and clear
These rows come from the same library as the filter above. Each one shows a comment that is common in client reviews, and a clearer version that says where, what and why. The client-side rows are written in the client’s voice; the reply rows are yours. The clear versions are longer, but they save a whole round of guessing.
| Situation | Direction | Vague version | Clearer version |
|---|---|---|---|
| The page feels flat | From the client | Can you make it pop more? | The “Book a table” button gets lost next to the photo. Can it stand out more, so it is the first thing people see? |
| A colour feels wrong | From the client | The colours are off. | The green on the buttons looks lighter than our brand green. Please use the green from our brand guide (page 4). |
| The logo feels too small | From the client | Make the logo bigger. | In the desktop header the logo looks small next to the menu. Can it be a little larger there? On phones it is fine as it is. |
| Praise that helps the next round | From the client | Looks great! | The checkout page is exactly right: short, clear and the total is easy to find. Please keep that style for the account pages. |
| Two people on the client side disagree | To the client | Your team can’t agree, so I’ll wait. | Maria asked for a bigger logo and Tom asked for a smaller one on phones. Which should I follow? If it helps, I can do bigger on desktop and keep phones as they are. |
| A request is outside the agreed scope | To the client | That’s not included. | A blog section is a great idea. It is not part of the current scope, so I will send a short quote for it today. The rest of your round 2 notes are all in hand. |
| Asking for a clear approval | To the client | So are we good? | All round 3 changes are done. If you are happy, please reply “approved” and I will prepare the final files. Anything after approval will be a new request. |
Using these design feedback examples well
Adapt the design feedback examples to your own project
The clear versions use made-up details, such as a “Book a table” button or a brand guide on page 4. Swap in your own pages, elements and dates. A guide that mentions a café when your client sells software will feel pasted.
Share the client guide before the first round, not after a bad one
Sent at kickoff, a short feedback guide reads as helpful. Sent after a vague round, it can read as a telling-off. Send it with the first review link and keep it to a handful of examples.
Clear feedback does not replace a review process
Even well-written comments get lost when they arrive across email, chat and calls. Agree on one place for feedback, a deadline for each round and one person who approves.
Push-back still needs the client’s decision
The reply examples explain trade-offs, but the client owns the final choice on their project. If they still want the bolder version after hearing why not, do it, note the decision, and move on.
Questions about design feedback examples
How do I give design feedback to a client without sounding rude?
Agree with the goal first, then explain the trade-off in their terms, then offer an option. “I can make all the text bold, but then the prices stop standing out. Could we make just the prices bold?” is firm without being a no.
Can I send these design feedback examples to my client?
Yes. Filter to “Feedback from clients”, pick the topics that fit the project, and use Copy as a client guide. It writes a short note with three habits and the examples shown, ready to paste into your kickoff email.
What should I do when client feedback is too vague to act on?
Ask a narrow question with choices instead of “what do you mean?”. For example: “Is it the headline, the button or the photo that feels flat?” A choice is easier to answer, and it gets you to a real request in one reply.
How should I reply when two people on the client side disagree?
Name both requests neutrally, ask the person who approves the work to choose, and offer a version that might satisfy both. Do not pick a side yourself; you will end up redoing the work when the other person sees it.
Is positive feedback worth asking clients for?
Yes. Praise that says what to keep, such as “the checkout page is exactly right”, stops good parts from being changed in a later round. Ask for it directly: “Which parts should stay exactly as they are?”
How do design feedback examples help with scope creep?
The reply set includes how to say a request is outside the agreed scope while still welcoming the idea. Separating it from the current round, and offering a quote, keeps the round moving and the price conversation calm.