You send the staging link on Friday with “let me know what you think.” The reply arrives on Tuesday: “can we make it pop,” from someone who wasn't on the kickoff call.
Nobody did anything wrong. A vague question got a vague answer. How to ask clients for feedback comes down to when you ask and what you ask, and both fit in one email and one short website feedback form. They're below, ready to copy.
Why is client feedback so vague?
Because nobody told the client where to look. Nielsen Norman Group's article on derailed design critiques opens its section on subjective feedback with a line every designer has heard: “I can't put my finger on it, but something feels off.” The author, Rachel Krause, puts the most common cause down to a lack of feedback guidelines: “When stakeholders and team members don't know where to focus, they'll give any and all feedback.”
The same article names a second cause, which is vocabulary. What a designer would call inconsistent kerning and line height, it says, a client may describe as “cluttered or needing more white space.” The client isn't wrong. They're describing a real problem in the only words they have, and the words don't say where it is.
So there are two jobs. Tell the client what kind of feedback you need, and give them a way to point.
When should you ask a client for feedback?
Once per round, on a version that holds still, with a date attached.
- Per round, not continuously. A client who can comment any time will comment at 9pm on a page you're halfway through changing. Agree the number of rounds up front and send one request for each.
- On a fixed version. Send a link that won't change during the review: a preview deploy or a staging address you leave alone until the deadline. If the page moves while the client is reading it, half the comments describe something that's already gone.
- With a deadline. Give a day and a time, and say what happens after it. “Comments by Thursday at 5pm, changes back to you the following Tuesday” is a schedule. “When you get a chance” is a wait.
What should you ask the client to review?
Scope the round before the client opens the link. Four things go in every request.
- What to review this round. Name the pages and the kind of feedback. Nielsen Norman Group's examples of guidelines are a fair menu: whether the design meets user goals, how it uses the brand and tone of voice, specific content questions, the overall look and feel. Pick the ones this round is for.
- What is out of scope. If the photos are placeholders and the blog isn't built, say so. Otherwise the first five comments are about the photos.
- Who decides. Ask the client to name one person with the final say, and ask for one agreed set of comments. When the marketing lead wants the headline shorter and the founder wants it longer, that's theirs to settle before it reaches you.
- One issue per comment. A paragraph that covers the logo, a typo and the pricing table can't be marked done. Three separate comments can.
How to ask clients for feedback in an email
Here is a request that carries all of that. Swap the bracketed parts and send it with each round.
Subject: [Project] round [2] of [3] is ready. Comments by [Thursday, 5pm]
Hi [name],
Round [2] is ready to review here: [link]. This version won't change while you're looking at it.
Please review: [the home page and the three services pages], on a phone as well as a laptop.
Please skip for now: [the blog and the photos, which are placeholders until round 3].
The questions I most need answered: [Does the home page headline say what you do? Are the service names and prices right?]
Please send comments by [Thursday at 5pm], one issue per comment. If people on your side see it differently, [name] has the final say, so please send one agreed set.
I'll make the changes and send round [3] on [date]. Anything that arrives after the deadline goes into that round.
It's short on purpose. Every line answers a question the client would otherwise have to guess at.
A website feedback form to copy
For the questions about the site as a whole, send a form with the email. This client feedback form has ten questions for a website review. Paste them into Google Forms, Typeform or a shared document, and cut any that don't apply to the round.
- Which version did you review? Paste the link and the date you looked at it.
- Who is filling this in, and whose views does it include?
- In one or two sentences, what is your overall impression?
- After ten seconds on the home page, is it clear what you do and who it's for? If not, what is missing?
- Does the site sound like your company? Quote one line that does and one that doesn't.
- Is anything factually wrong, such as a price, a name, a date or a service? Give the page and the correct text.
- Is anything missing that a customer would look for before getting in touch?
- Did anything not work, such as a link, a form or a button? Tell us the page, what you clicked, what happened, and the device and browser you were using.
- Which changes must happen before launch, and which would be nice to have? List the must-haves in order.
- Once the changes above are made, do you approve this round? Yes, or no and we need to talk.
Question 2 flushes out the reviewer you didn't know about. Question 9 makes the client rank, which a comment thread never does. Question 10 gives the round an end. For the testing side of a review, the website QA and launch checklist covers what your own team should check before the client sees anything.
Where does a feedback form fall short?
Look at questions 6 and 8. Each one asks the client to describe a place: the page, the thing they clicked, the text that's wrong. That's the part clients find hard, for the reason Nielsen Norman Group gave. They know which button they mean. Writing it down so that you know too is work, and “the green one near the bottom” is what that work produces.
A form can't point. For anything that lives at one spot on one page, it's quicker to let the client click that spot and type the comment there, which is what annotating a website means in practice.