Every website project has the same hidden cost: the revision loop. A designer sends a mockup, the client replies with a few lines of comments, the designer guesses at what they meant, and two weeks later everyone is frustrated and the homepage still is not signed off.
Here is the uncomfortable truth we have learned after years of building sites at spal.me: the quality of a design rarely depends on the designer alone. It depends on the quality of the feedback loop between the designer and the client. Great feedback does not require design vocabulary or a degree in typography. It requires being specific about what bothers you, where it is, and why it matters for your business.
This guide shows you exactly how to give feedback to a web designer, with side-by-side examples of weak versus strong revision requests, a copy-paste template, and the process we use with our own clients to cut projects from five revision rounds down to two.
Why Vague Feedback Costs You Money
“Make it pop” is the most famous example, but it has plenty of cousins: “it feels off”, “I am not loving it”, “can it look more premium?”, “my wife thinks the blue is weird”. launchthedamnthing.com makes the same point with more data.
None of these are bad intentions. They are simply reactions, not instructions. And here is what happens when a designer receives a reaction:
- They guess at the underlying problem (maybe contrast? maybe hierarchy? maybe the photo?).
- They make a change based on that guess.
- There is roughly a one-in-three chance the guess was right.
- You review again, still unsatisfied, and the round repeats.
Each round typically costs 3 to 5 business days and, in fixed-scope contracts, eats into the budget you would rather spend on extra pages, animation or SEO work. Most studios include two or three rounds of revisions. Vague feedback is how clients burn through all of them on the homepage hero section.
The one mental shift that fixes 80% of it
Report problems, do not prescribe solutions. You are the expert on your business, your customers and your goals. Your designer is the expert on layout, hierarchy and conversion patterns. When you say “make the logo bigger”, you have handed over a solution and removed the designer’s ability to solve the actual problem, which might be that the logo lacks contrast against the background, not size.
| You are tempted to say | Say this instead |
|---|---|
| “Make the logo bigger.” | “On mobile, I scrolled past the header without registering who we are. Can we strengthen brand recognition at the top?” |
| “Make it pop.” | “The ‘Book a call’ button does not draw my eye first when I look at the page for three seconds. It should be the first thing people notice.” |
| “It feels cheap.” | “Our clients are law firms paying 10k+ retainers. The bright gradients feel closer to a startup app than a professional practice.” |
The 9 Rules for Giving Feedback a Web Designer Can Actually Use
1. Anchor every comment to a location
A designer receiving “the spacing is weird” has to scan eight sections looking for the offender. Always name the page, the section, and ideally the device.
Weak: “Something looks off with the spacing.”
Strong: “Homepage, the three-column services block, desktop view: the gap between the headline and the first card looks much tighter than the gap below the cards.”
If your designer shares work in Figma, a tool like BugHerd, or a staging URL, leave the comment pinned directly on the element. A pinned comment removes 100% of the location guesswork.
2. Separate “broken” from “preference”
Not all feedback carries the same weight, and mixing them creates confusion about priorities. Tag each comment with one of three labels:
- Blocker: factually wrong or broken (wrong phone number, broken link, text overlapping on mobile).
- Business: the design does not serve a business goal (the pricing table hides the plan we want to sell).
- Preference: a taste-based opinion (I prefer a warmer photo).
This single habit tells your designer where to spend their hours. Blockers get fixed, business issues get discussed, preferences get weighed against best practice.
3. Explain the “why” behind the reaction
You do not need to know the fix. You do need to describe the effect the design had on you.
| Weak request | Strong request |
|---|---|
| “I do not like the About section.” | “The About section reads like a company history. Our buyers care about whether we have done this in their industry, so trust signals would work harder than the timeline.” |
| “Too much white space.” | “I have to scroll four times to reach the contact form. I would like the main conversion point to be reachable faster.” |
| “Change the font.” | “The body text is hard for me to read on my laptop, and half our audience is over 55. Can we improve legibility?” |
4. Consolidate feedback into one document, from one person
The single biggest project killer is not bad taste. It is five stakeholders sending contradictory emails over four days.
Before you reply to a design, do this:
- Circulate the mockup internally with a deadline (48 hours works well).
- Collect every comment in one shared document or one commenting tool.
- Resolve internal contradictions before sending. If the CEO wants a video hero and marketing wants a form, decide internally or flag it explicitly as an open question.
- Nominate one point of contact who sends the final consolidated list.
A single consolidated list turns three chaotic rounds into one clean one.
5. Show examples, and explain what you like about them
Reference links are gold, but only when annotated. “I like stripe.com” is useless because Stripe does a hundred things at once.
Strong: “I like how stripe.com uses a single short headline with one clear button, no competing elements. I am not asking for the gradients or the animation, just that clarity.”
Equally valuable: share what you dislike and why. Negative references narrow the field fast.
6. Never review a design on the wrong screen
A surprising share of “the text is tiny” feedback comes from clients reviewing a desktop mockup zoomed out to 50% on a laptop, or a mobile screen viewed at full size on a 27-inch monitor.
- Ask your designer for a clickable prototype or staging link, not a flat JPEG, whenever possible.
- View desktop designs at 100% zoom.
- Open the mobile version on an actual phone.
- Note the device and browser in your comment if something looks broken.
7. Judge the layout, not the placeholder content
Early rounds often use stock photography and draft copy. If you spend your feedback budget on “that is not our team in the photo”, you have used a round without improving the design.
Ask your designer one question up front: “What should I review in this round, and what is still a placeholder?” Any process-driven studio will tell you plainly. At spal.me we label each deliverable with exactly what is up for review so nobody wastes a cycle.
8. Be honest, be direct, and say what is working too
Designers do not need to be protected from an honest “this is not right”. What they cannot work with is polite vagueness that hides a real objection, which then resurfaces two rounds later as “I never liked that section”.
At the same time, tell them what to keep. If you only list problems, a designer may rebuild something you actually loved.
Strong: “Keep the hero exactly as it is, it nails the tone. The services section below it is the part that is not working for me.”
9. Ask questions instead of issuing orders
Some design decisions look strange but are deliberate: an asymmetric layout to create motion, low-contrast secondary buttons to protect the primary call to action, a shorter menu to reduce decision fatigue.
Before demanding a change, ask: “Can you walk me through why the navigation only has four items?” You will either get a reason that satisfies you (saving a revision round) or you will expose a genuine oversight. Either way, you win.
A Copy-Paste Feedback Template
Use this structure for every round. It takes five minutes and it is the single fastest way to reduce revisions.
| Field | Example |
|---|---|
| Page / Section | Homepage, testimonial slider |
| Device | iPhone 15, Safari |
| Type | Business (not a blocker) |
| What I observe | Only one testimonial is visible and there is no client logo next to it |
| Why it matters | Social proof is our strongest sales argument, prospects always ask who else we work with |
| Priority | High |
| Reference (optional) | Link + one line on what specifically you like about it |
Weak vs Strong: More Real Examples
| Vague comment | What the designer hears | Actionable version |
|---|---|---|
| “Can we try a few options?” | Nothing. Unlimited scope. | “Could we see two versions of the hero: one image-led, one text-led, so we can compare?” |
| “The colors are not right.” | Which colors? Brand? Accents? Background? | “The orange accent appears on buttons, icons and headings, so nothing stands out. Can we reserve it for buttons only?” |
| “Add more content here.” | How much? Written by whom? | “I am sending 120 words of new copy for this section today. Can the layout hold three short paragraphs plus an icon?” |
| “It is too busy.” | Remove… something? | “When I land on the page I count five things competing for attention. I want visitors to see the headline first, then the demo button.” |
| “My colleague hates it.” | Unanswerable. | “Our sales lead finds the pricing page confusing because the plan differences are not scannable. Can we add a comparison table?” |
How to Review a Website Design, Step by Step
Do not open the mockup and start reacting. Run this 20-minute review process instead:
- The five-second test. Open the page, look for five seconds, close it. Write down what you remember. If you cannot state what the company does and what to do next, that is your first and most important comment.
- Check it against the brief. Pull up the original goals. Does the design serve them? A beautiful page that does not drive enquiries is a failed page.
- Walk the user journey. Pretend to be your most important customer type. Can they find pricing, proof, and a way to contact you within two clicks?
- Review on mobile. Most traffic is mobile. Review mobile first if you only have time for one.
- Proofread facts. Phone numbers, addresses, service names, legal wording, spelling of names.
- Only then, aesthetics. Colors, photography, typography. Last, not first.
- Write the consolidated list using the template above, ordered by priority.
What to Avoid Completely
- Design by committee vote. Averaging seven opinions produces a design nobody wanted.
- Feedback in six separate channels. Pick one place. Email chains, WhatsApp messages and verbal notes in calls will get lost.
- Reopening settled decisions. If the layout was approved in round one, do not restructure it in round three without acknowledging it as new scope.
- Design edits in the wrong format. Sending a Word document with your own attempted layout usually creates more work than a clear paragraph of text.
- Silence. A designer waiting six days for feedback loses context and momentum. Even “we need until Friday” is useful.
How We Handle Revisions at spal.me
We build the feedback process into the project from day one, because a smooth loop is cheaper for you and faster for us:
- Every deliverable ships with a note stating what is up for review and what is still placeholder.
- Comments are pinned directly on the design or the staging site, never buried in email.
- Each round has a stated deadline on both sides so nothing stalls.
- We flag when a request crosses into new scope before doing the work, so there are no surprise invoices.
- We explain the reasoning behind design decisions, so you can approve with confidence rather than on instinct.
Clients who use the template in this article typically sign off in two rounds instead of four or five. That is often two to three weeks off the launch date.
FAQ
How do you give feedback to a designer?
Point to a specific location (page, section, device), describe the problem you observe rather than prescribing a fix, explain why it matters for your business or your users, and mark its priority. Consolidate all stakeholder comments into one list from one person, and include what is working well alongside what is not.
What are good design feedback examples?
Good: “On the mobile homepage, the ‘Get a quote’ button sits below three scrolls of text, and quotes are our main conversion goal, so I would like it reachable sooner.” Bad: “Make it pop.” The difference is location, observed problem, and business reason.
Is it rude to tell a designer I do not like the design?
Not at all. Professional designers prefer direct honesty over polite vagueness, because vagueness costs everyone time. What matters is explaining what is not working and why, rather than just delivering a verdict. “This does not feel right for our audience because X” is far more useful than silence or false enthusiasm.
How do I appreciate or compliment my designer?
Be as specific with praise as with criticism. “The way you grouped the services into three tiers made our offer instantly clearer” is worth more than “looks great”, because it tells the designer which decisions to keep and repeat across the rest of the site. Public reviews, referrals and prompt payment are also genuinely appreciated.
How many rounds of revisions are normal for a website?
Most studios include two to three rounds per design phase. With consolidated, specific feedback, two rounds is usually enough. Scattered or contradictory feedback is the main reason projects exceed that and drift into additional billable work. It is argued more carefully on bugherd.com.
What tools make website feedback easier?
Commenting directly on the design or staging site is ideal: Figma comments for mockups, and tools like BugHerd, Markup.io or Pastel for live and staging pages. They capture the URL, browser and screen size automatically, which eliminates most of the back and forth. A simple shared spreadsheet with columns for page, issue, priority and status also works well.
Should I give feedback on copy and images in the first round?
Only if they are final. Ask your designer what is placeholder before you comment. In early rounds, focus on structure, hierarchy and whether the page serves your business goals. Save content polish for later rounds once the layout is approved.
Planning a new website or a redesign? If you want a studio that treats the feedback loop as part of the design work rather than an afterthought, get in touch with the team at spal.me and we will walk you through our process before you commit to anything.