Most vague website feedback is not careless. A client sees something that feels wrong, but they do not have the vocabulary—or enough context—to explain why. So the agency receives “make it pop,” “this feels off,” or “can we make this more conversion focused?”
Those comments describe a reaction, not a direction. If your team guesses what the client meant, the next version may be beautifully executed and still wrong. If you schedule a call for every unclear note, the review process becomes the project.
Clear feedback connects three things: the element being discussed, the outcome the client wants, and the constraint the solution must respect.
Ask for the missing decision
A useful follow-up question should not ask the client to repeat the comment in different words. It should identify the one decision that would materially change the work.
For example, “Can we make this headline more conversion focused?” might mean the client wants more demo requests, clearer positioning, stronger urgency, or a different audience emphasis. Asking “Can you be more specific?” leaves all of those possibilities open. Asking which outcome matters most closes the important gap.
Use a simple three-part process
- Anchor the comment to the work. Collect feedback on the exact element whenever possible. A comment attached to a headline is more useful than the same comment in an email thread.
- Separate preference from objective. “I do not like this green” may be a simple preference. “This does not feel premium” points to a business or brand objective. The second deserves clarification.
- Ask one bounded question. Offer two or three plausible directions and an escape hatch. This is easier to answer than an empty text box and reveals the tradeoff the client actually cares about.
Do not clarify everything
Clarification becomes annoying when it appears after every comment. “Change this button to blue” is already actionable. So is “Replace the pricing copy with the approved paragraph in the brief.” A follow-up is valuable only when different reasonable interpretations would produce meaningfully different work.
A good system stays out of the way for explicit requests and steps in for comments about tone, hierarchy, emphasis, audience, or outcomes. That selectivity is what makes the question feel helpful rather than procedural.
Turn the answer into an implementation-ready task
The clarification is not the finish line. Combine the original comment, selected element, page context, and the client’s answer into one concise task. Preserve the client’s intent, name the element, and describe the expected outcome. Your designer or developer should not have to reconstruct the conversation.
This closes the loop while the client still remembers what they were reacting to—and before your team invests time in the wrong interpretation.