Good website design feedback is specific, tied to a goal and collected in one place. Say what to change, where and why, using annotated screenshots, and send one consolidated list per round rather than scattered WhatsApp messages. Agree in advance how many revision rounds are included, often 2, and who gives final approval.
Key Takeaways
- Specific comments tied to customers or goals get better results than personal taste.
- Annotated screenshots remove guesswork about which element you mean.
- Collect feedback from everyone, resolve disagreements internally, then send one list.
- Know how many revision rounds your contract includes.
- Approve designs in writing, so the build can start on a fixed basis.
Why Does Website Design Feedback Matter So Much?
The design stage is where many website projects stall. The developer sends a design; the owner replies "not quite right, make it pop"; two partners send different opinions on WhatsApp; a relative suggests a new colour. Weeks pass in revisions that never settle. Clear website design feedback fixes this. It helps the designer understand what you want, keeps revision rounds within the contract and gets the site launched on time.
Feedback habits matter whichever firm you hire; see how to pick a development company for that first step.
What Does Good and Vague Feedback Look Like?
| Vague feedback | Useful feedback (illustrative) |
|---|---|
| "Make it pop." | "The main button blends into the background. Make it stand out more so visitors notice it." |
| "I don't like the colours." | "The grey feels dull for a children's clothing brand. Try our logo's orange as the accent." |
| "Change the homepage." | "On the homepage, move the WhatsApp button above the services section on mobile." |
| "Looks too empty." | "Add our three main services as cards under the headline." |
| "My brother thinks it should be blue." | "Our customers are mostly mothers; does the design feel warm enough for them?" |
The useful versions say what, where and why. The why lets the designer suggest a better solution than the one you first imagined.
How Should You Point to Specific Elements?
Take a screenshot, draw a box or arrow on the element and number it, then write numbered comments. Most phones and computers have built-in markup tools. Say whether a comment applies to desktop, mobile or both. Many design tools and staging sites also allow comments pinned directly on the page, which is even clearer.
Why Send One Consolidated List?
When several people give feedback separately, the designer receives contradictions and does not know whose view wins. Collect comments from everyone involved, discuss disagreements internally, and send one agreed list per round, from one person. Our contract checklist recommends naming that person in the agreement.
How Many Revision Rounds Are Normal?
Contracts commonly include a set number of design revision rounds, often two, with further rounds charged. A round means one consolidated list and one revised design. Small fixes such as typos are usually not counted. Know your allowance before you start, and use rounds for meaningful changes. Our guide to change requests explains how extra work is priced.
What Should You Focus On?
- Clarity: can a visitor tell in five seconds what you do?
- Action: is the main call to action obvious on mobile?
- Accuracy: are services, prices, addresses and phone numbers correct?
- Trust: do photos and wording feel like your real business?
- Taste: colours and fonts last, unless they clash with your brand.
Should You Review on a Phone?
Yes. Most of your visitors will see the site on a phone, so review the mobile design first, ideally on your own phone, not only the desktop layout on a large screen. Check that text is readable without zooming and buttons are easy to tap.
How Should You Approve the Design?
When the design is right, approve it in writing: an email or message saying the design is approved for build. This fixes the design so building can start, and makes later design changes clearly separate. Our websites, from Rs 40,500, include agreed design rounds and written approval stages.
How Should Feedback Be Worded?
Be direct but polite, and describe problems rather than prescribing pixel-level fixes. "Visitors may miss the booking button" invites a good solution; "move it 20 pixels left" may not solve the real issue. Mention what you like, too, so the designer knows what to keep.
What About Sharing Designs?
Designs may include unreleased products or prices. Share preview links only with people who need to give feedback, and ask the developer to password-protect staging sites.
Talk to Us
See our contact page to start a project.
See also Your First Website Discovery Meeting.
Frequently Asked Questions
- W3C WAI — WCAG overview
- web.dev — Responsive web design basics
- Google Search Central — Mobile site and mobile-first indexing
How we researched this: Feedback examples are invented for illustration. The advice on rounds, consolidation and approval is editorial, based on common contract practice; two rounds is described as common, not universal. Our prices come from the published list.
Stuck in endless design revisions?
Message us on WhatsApp for a fixed quote, or see our published pricing first.