The first time you see a design for your new website is exciting, and a little daunting. You know something feels right or wrong, but turning that feeling into feedback a designer can act on is harder than it looks. “Can it pop more?” and “I don’t love it” are honest reactions, yet they leave everyone guessing.
Good feedback is one of the biggest factors in how smoothly a website project runs. It saves revision rounds, keeps the design focused on your customers and avoids the frustration of a site that ends up designed by committee. This guide gives you a simple way to review designs well.
The short answer
To give useful feedback on a website design:
- Review against the goals agreed in the brief, not personal taste alone.
- Look at the big picture first: structure, content and clarity, before colours and fonts.
- Describe the problem, not the solution: “I can’t tell what we offer” rather than “make the logo bigger”.
- Be specific about where and why something doesn’t work.
- Combine feedback from colleagues into one clear list, with one person responsible for decisions.
Start with the brief
Before opening the design, re-read what you agreed at the start: who the site is for, what visitors need to do, and what success looks like. Our guide to writing a website brief explains why those goals matter. A design that you personally dislike can still be right for your customers, and one you love can miss the point.
Ask of every page:
- Would our typical customer understand what we do within a few seconds?
- Can they find the information they came for?
- Is the next step, such as an enquiry, obvious?
- Does it feel like our business?
Review in the right order
Feedback works best from the largest questions to the smallest. Commenting on button colours when the page structure is still wrong wastes a round of revisions.
| Order | Focus | Example questions |
|---|---|---|
| 1 | Structure and content | Are the right sections there, in the right order? Is anything missing? |
| 2 | Clarity and hierarchy | Is the most important message the most prominent? |
| 3 | Brand and feel | Does it reflect our personality and audience? |
| 4 | Visual details | Colours, imagery, spacing, icons |
| 5 | Wording and small fixes | Typos, labels, exact phrasing |
Our guide to visual hierarchy explains how designers decide what draws the eye first.
Describe problems, not solutions
When you see something that doesn’t work, describe the effect it has on you or your customers, and let the designer propose the fix. You are the expert on your business; the designer is the expert on how to solve design problems.
- Instead of “Make the headline red”, try “The headline gets lost against the photo.”
- Instead of “Add more images”, try “The services section feels hard to scan.”
- Instead of “Use a different font”, try “This feels more playful than our clients expect.”
If you do have a specific idea, share it as a suggestion along with the reason. The reason is what helps the designer find the best solution, which might be different from your first idea.
Be specific
Vague feedback leads to guesswork. Point to the exact place and explain why:
- “On the pricing page, the second paragraph repeats what the heading already says.”
- “On mobile, I had to scroll past three sections before I saw how to contact us.”
- “The photo in the hero shows an office, but most of our work happens on site.”
Screenshots with notes, or comments pinned directly on the design in a tool such as Figma, are much clearer than a long email.
Look at it the way visitors will
- Check mobile designs properly. Many visitors will see the phone version first, so review it as carefully as the desktop layout. See our guide to mobile-first design.
- Use real content. Placeholder text hides problems. If real copy isn’t ready, the design may change once it is.
- Read it fresh. Look at the design once quickly, as a visitor would, before studying the details.
- Show it to a customer if you can. A short reaction from someone in your target audience is worth more than several internal opinions.
Gathering feedback from several people
Websites often involve several people: an owner, a marketing lead, sales staff and partners. Different opinions are useful, but contradictory feedback slows projects down.
- Choose one decision-maker who has the final say and sends feedback to the designer.
- Collect comments in one place and remove duplicates.
- Resolve contradictions internally before sending. The designer can’t choose between two colleagues.
- Separate must-haves from preferences, so the designer knows what matters most.
- Stick to the agreed timeline. Late feedback from someone who wasn’t involved earlier often reopens settled decisions.
Feedback to avoid
- “I’ll know it when I see it.” It turns design into guessing.
- Asking for everything to stand out. If everything is emphasised, nothing is.
- Designing for yourself rather than your customers.
- Copying a competitor’s site without explaining what you like about it.
- Introducing new requirements late in the design phase without discussing the impact on time and cost.
A simple feedback format
If you are unsure how to write your comments, use the same four parts for each one:
- Where: the page and section, for example “Home, services block”.
- What you noticed: the effect, for example “I couldn’t tell which service suits a small clinic”.
- Why it matters: the link to the brief, for example “clinics are our main audience”.
- Priority: must change, should change, or a minor preference.
A list in this format is quick to write and easy for a designer to work through. It also makes the next review faster, because you can check each item off and see exactly what changed.
Frequently asked questions
How many rounds of design revisions are normal?
It depends on the agreement, but most projects include a set number of revision rounds for each stage. Clear, combined feedback means each round makes real progress, so you rarely need more.
Is it all right to say I don’t like a design?
Yes, but explain why. A designer can work with “it feels too corporate for our clients” far more easily than with “I don’t like it”. Honest feedback early is better than polite approval followed by doubts later.
What if my team disagrees about the design?
Go back to the brief and the customers. Ask which option better serves the visitor’s goals, and let the agreed decision-maker choose. If the disagreement is fundamental, a quick test with a few real customers can settle it.
What to do next
Before your next design review, print or open the brief alongside the design, review structure before details, and write every comment as a problem with a location and a reason.
Our website design and development projects include agreed revision rounds at each stage, so you always know where feedback fits. If you are preparing for a project, our project brief helps set the goals your feedback will be measured against.