How to Give Useful Feedback on Website Designs
Good feedback makes a website project better. Vague or scattered feedback makes it slower. The goal is not to approve everything immediately. The goal is to respond in a way the design team can act on.
Review the design against the brief
Start by comparing the design to the project goal. Does it support the audience? Does it make the service clear? Are the calls to action obvious? Does the design match the brand direction agreed in discovery?
Be specific
“I do not like it” is hard to solve. “The heading feels too soft for our industry” or “the quote button is not visible enough on mobile” gives the designer something practical to adjust.
Group feedback before sending
Collect feedback from internal stakeholders before sending it through. One clear list is easier to action than several separate messages with conflicting requests.
Useful feedback examples
- This section needs to make the service outcome clearer.
- The enquiry button should be more prominent above the fold.
- The imagery feels too corporate for our audience.
- This page needs a stronger proof point before the form.
- The mobile version should make the next step easier to reach.
Mistakes to avoid
- Giving feedback before reading the full page.
- Commenting only on personal taste instead of user needs.
- Sending contradictory feedback from multiple people.
- Requesting major content changes after design approval.
- Approving desktop without reviewing mobile.
FAQ
Should feedback be visual or written?
Both can work. Marking comments directly on a design or staging page is often clearer than describing the issue in a separate email.
How many rounds of feedback are normal?
That depends on the scope, but feedback rounds should be defined before the project starts.
What if stakeholders disagree?
Return to the project goal and target customer. The best decision is usually the one that helps users understand and act.
Next step
Read Leave Feedback during a Design Development Project for the tools we use during review.
View the Feedback Guide
