How to give website design feedback that gets you the result you want

The most useful design feedback describes a problem from your customer's point of view, comes from one person and arrives in one batch. Feedback like that gets you a better website in fewer rounds. Most projects include a set number of revision rounds, so how you use them matters. Here is a practical method.

Key takeaways

• Judge the design against the goal in your brief, and treat personal taste as a smaller factor.
• Describe the problem you see and let the designer propose the fix.
• Collect all comments into a single document from one person per round.
• Review on a phone as well as a laptop, with real content.
• Separate must-fix items from preferences, and approve in writing.

Start from the goal, not from taste

Before you open the design, reread what the site is supposed to achieve and who it is for. Then ask whether a visitor from that group would understand the offer, trust the business and know what to do next. A design can be attractive and still miss the goal, and the reverse is also true.

Personal taste still counts, because it is your brand. Mention it, and label it as preference.

Describe the problem, not the solution

"Make the button bigger" prescribes a fix. "I did not notice how to book a call" describes a problem, and the designer can solve it in several ways, such as contrast, position or wording. Describing the problem keeps the full range of solutions open and avoids the situation where you have fixed one symptom and left the cause.

A good comment has three parts: where you are on the page, what you expected and what happened instead.

Give feedback in one voice

If three colleagues send separate comments, the designer receives contradictions and has to guess who decides. Nominate one person to gather the comments, resolve disagreements internally and send one list. Number the items so that the answers can refer to them.

This is the single change that most often saves a round.

Look at it the way your customers will

Open the design on your phone, because for many businesses most visitors arrive on mobile. Read it with real text and real photos, since placeholder content hides problems with length and tone. Try to complete the main action, whether that is calling, booking or sending a message, and note how many steps it took.

Then ask someone who does not know your business to describe what you do after looking at the first screen for five seconds. Their answer tells you more than a long internal discussion. Our seven-check review lists other things worth testing.

Sort the list: must-fix and nice-to-have

Mark each comment as one of three types. A must-fix blocks the goal or contains an error, such as a wrong phone number. A should-fix improves clarity or trust. A preference is a matter of taste. When there are many comments, the designer can then spend time where it matters most, and you keep the freedom to drop items you decide are minor.

Use your revision rounds on purpose

A project usually includes a limited number of rounds, so the first round is best spent on the biggest points: structure, message and the main action. Fine detail such as exact spacing and small wording changes belongs in the later round, once the big decisions are settled. Adding new ideas late in the project is the most common way to run out of rounds. If a genuinely new requirement appears, say so and let the studio quote it separately.

Approve clearly

When you are happy with a stage, say so in writing, for example by email. Clear approval lets the next stage start on solid ground. It also protects you, because it records exactly what was agreed.

For the bigger picture of how a project runs, read how a website project works. If you want advice on layout choices, our conversion design principles explain what we look for, and a free 30-minute discovery call is the place to talk about your own site. The free website audit gives you an independent starting point.