How to Give Useful Feedback on a Website Design
By CodexierPublished 5 min read
The first design draft of a new website often triggers a gut reaction, and gut reactions make poor instructions. Feedback like 'make it pop' or 'something feels off' sends the designer guessing, and every guess is a revision round you pay for in time or money. This guide shows how to review a design against what the site must achieve, collect colleagues' opinions without design by committee, and write comments that lead to a better second version.
Review against goals, not taste
Personal taste matters less than you think, because you are not the target visitor. A useful test is to open the design and pretend to be your typical customer arriving from a Google search. Can you tell within five seconds what the company does, where it operates and how to get in touch or book? If yes, most of the remaining feedback is polish.
- Does the homepage headline say what you do in plain words?
- Is the main call to action visible without scrolling on a phone?
- Do the service pages answer the questions customers actually ask you on the phone?
- Are trust signals visible: organisation number, real address, reviews, clear pricing or a price range?
- Does it work on mobile first? Most visitors to a Swedish small-business site arrive on a phone.
Collecting feedback from colleagues
Involving colleagues is good: the salesperson knows which questions customers ask, the person answering the phone knows what confuses them. The risk is ten conflicting opinions sent straight to the designer. Avoid it with a simple routine.
- Pick one owner who consolidates and decides. Everyone else advises.
- Give reviewers the brief and three questions to answer, rather than asking what they think.
- Set a deadline, often two or three working days, and collect comments in one shared document.
- The owner removes duplicates, resolves contradictions and ranks by importance before sending.
Writing specific, actionable comments
A good comment has four parts: where, what, why and how important. Compare these examples.
| Vague | Actionable |
|---|---|
| The homepage feels boring | Homepage hero: the photo does not show our work, so visitors cannot tell we renovate bathrooms. Must fix. |
| Make the button bigger | Service pages: the booking button is below the fold on mobile, customers may miss it. Must fix. |
| I don't like the colours | The pale grey text on white is hard to read for older customers. Check contrast. Should fix. |
| Can we add more stuff? | Pricing page: customers always ask about ROT deduction. Add a short explanation. Nice to have. |
Priority labels such as must, should and nice to have help the designer spend the round where it matters.
Comment on the design in context: annotate screenshots or use the comment tool in Figma or the preview link rather than describing positions in an email. And separate content from design. If a text is wrong, send the corrected text; do not ask the designer to rewrite your service description.
Rounds, deadlines and scope
Most fixed-price website projects include a set number of revision rounds. A round is one consolidated batch of feedback, not every email you send. Sending comments piecemeal can burn through rounds or delay the whole project, because the designer cannot start until the list is complete.
Scope is a separate question. A comment that asks for a new page, a new feature or a changed structure is a change request, not feedback on the design. Clarifying this early protects both sides. A clear website brief at the start makes it much easier to tell a correction from a new wish, and our website launch package lists what each round covers.
Approving and moving on
Perfection is not the approval standard. The standard is that the design meets the brief and has no must-fix issues left. Approve in writing, list any small items that can be handled during development, and move on. A site that launches and is then improved from real visitor behaviour beats one that is polished for months in preview.
When not to buy from us: if you want unlimited rounds until everything feels right, a fixed-price package is the wrong model and hourly design work fits better. If you want to talk through how feedback works in our process before you commit, book a free call.
Frequently asked questions
How many revision rounds are normal?
Two or three consolidated rounds is common in fixed-price website work. What matters more than the number is that each round is one complete list from one decision-maker.
Should I suggest the solution or just the problem?
Describe the problem and why it matters. You can add an idea, but let the designer propose the fix; they often know a solution that solves the problem without breaking something else on the page.
What if my colleagues disagree about the design?
Return to the brief and the target customer. The question is not who is right but which option helps the visitor find the next step. If it is still unclear, test both with a few real customers.
Is it too late to change the structure after the design is shown?
Not too late, but usually a change request. Structure and page list should be settled in the brief or wireframe stage, which is why that step exists.
Planning a new website and want a smooth review process?
Tell us what the site must achieve and who will approve it. In fifteen minutes we can walk through how our design rounds work and what a realistic timeline looks like.
Book a free 15-minute call