Set the purpose of each review
A client may say “I’m not sure it feels right” because they have not been told what kind of decision they need to make. Before sharing a draft, explain what stage the work has reached and what feedback would be useful now. An early concept review might focus on direction, audience and priorities. A later review might focus on whether the agreed content is accurate and the details are ready for delivery.
Put the purpose in the message that accompanies the work, not only in a meeting agenda. For example: “This round is for choosing a visual direction. Please focus on whether the overall style suits your audience; we can refine spacing and copy after we agree on a direction.” This gives the client permission to respond without treating every visible detail as final.
Ask questions that point to a decision
“What do you think?” is easy to ask but hard to answer. Replace it with a few questions tied to the project brief. For a homepage design, you might ask: “Is the main offer clear within the first section?” and “Which of these two layouts makes the next step easiest to understand?” For an illustration, ask whether the mood fits its intended use and whether any essential subject matter is missing.
Keep the list short enough that the client can respond thoughtfully. Questions work best when they identify both the thing to assess and the reason it matters. “Does this feel modern?” may lead to conflicting tastes; “Does this style fit the approachable tone we agreed on?” connects the answer to a shared goal. If you need approval on one choice, name that choice directly rather than hoping it emerges from general comments.
Make it easy to locate and explain a concern
Clients do not need design vocabulary to give useful feedback. Offer a simple pattern they can use: identify the element, describe the concern, and explain the effect they want instead. A comment such as “The button near the top is hard to notice, and we want visitors to see the booking option quickly” gives you more to work with than “Make it pop.” You can then propose a suitable design change rather than asking the client to invent one.
Give reviewers a clear place to leave comments, whether that is an annotated file or a shared document with page and section references. If several people are reviewing, ask the client to combine their responses and flag any unresolved disagreements before sending them over. This reduces the chance of acting on two incompatible requests while keeping the client responsible for internal decisions.
Clarify vague or conflicting notes without sounding defensive
When feedback is unclear, start by reflecting what you heard. “It sounds like the page feels too formal for the audience. Is the main concern the imagery, the language, or both?” This shows that you are taking the comment seriously while narrowing the decision. If a requested change conflicts with the brief, explain the trade-off in project terms: “We can add more information here, though it may make the primary action less prominent. Which outcome matters more for this page?”
Avoid asking the client to justify a preference as if it were a mistake. A preference may reflect knowledge you do not have, or it may simply need to be weighed against the agreed objectives. Ask what prompted the request, then distinguish a requirement from an option to explore. When helpful, offer two practical paths and state what each would change. The aim is to reach a decision, not to win a debate about taste.
Close the loop with a revision plan
After a review, summarize the feedback in your own words before revising. Group comments into decisions, changes and open questions. For example: “We’ll keep direction B, make the booking link more visible, and shorten the introduction. You’ll confirm the service names before I update the copy.” This gives both sides a chance to catch misunderstandings while changes are still easy to discuss.
For each revision round, say which notes you are addressing and what you need from the client next. If a new request expands the work beyond the agreed scope, separate it from the current revision and discuss its impact before starting it. Specific feedback is not just more detail in a comment thread; it is a shared understanding of the problem, the desired outcome and the next decision.
