How to collect client feedback on design work
To collect client feedback on a design, send them a written review brief with specific questions — not an open-ended "what do you think?" — so they respond to the right things. For visual work, a shared link they can pin comments directly onto beats email attachments, which spawn version confusion the moment someone saves a copy.
Send a written review brief before they look
Vague prompts get vague feedback. Before your client opens the file, send three or four questions tied to the project goal: "Does the hierarchy match how you'd explain the product verbally?" or "Does the color feel right for the audience we discussed?" Avoid "do you like it?" — that invites gut reactions rather than direction. A short context paragraph reminding them of the goal (not the design decisions you made) helps them evaluate rather than react. Send the brief at the same time as the design, not after. Clients who read the questions first look at the design with a framework; clients who see the design first anchor on whatever caught their eye.
Walk them through it on a short recording
A two-minute Loom recording of you narrating the design cuts revision cycles in half. Show the design the way you'd present it in a meeting: explain what problem each section solves, flag the decision you want their input on, and name the things that are intentional (so they don't flag those). Keep it under three minutes — most clients won't finish a longer one. This is especially useful when your client is the decision-maker but will share the design internally before responding; your narration travels with it. Tools: Loom, Wistia, or QuickTime + a shared folder link. Share the recording URL with the design in one message.
Use a structured feedback form for the first round
A short Google Form or Typeform with four to six fixed questions collects structured feedback faster than a freeform email thread. Useful questions: "Rate how well this matches the brief (1–5)", "Which section needs the most work?", "Is there anything here you'd want your team to see before we proceed?". Fixed questions also prevent the feedback from spiraling into scope additions. One gotcha: don't use a form for detailed visual feedback — clients can't point at the specific element they mean, so you'll spend follow-up calls interpreting "the logo area" or "the top bit". Use the form for sentiment and priority; use a visual tool for the specific changes.
Share a link they can annotate directly — not a file
Email attachments cause a specific failure: the client downloads the file, marks it up in Preview or Acrobat, re-saves it with their name in the filename, and emails it back. Now you have a separate file with comments that aren't linked to the live version. The cleaner path is a shared link they open in a browser and click on the exact element they mean — a headline, a graphic, a specific button — and leave a pinned comment there. Every note lands on the same artifact, in one thread, anchored to the spot. You reply in context, push a revision, and the comment history travels with the link. No "v3 FINAL (2) John edits.pdf".
Consolidate before you act
Before you open a design file, consolidate all feedback into a single prioritized list. If feedback came from multiple people on the client's team, ask for one consolidated response — competing notes from two stakeholders waste a revision round. Read the feedback against the original brief: a note that contradicts the agreed goal is worth flagging before acting on. A simple rule: resolve conflicts with a question, not a design change. "You mentioned the type feels small but the brief called for accessibility AA compliance — want me to flag the options?" is faster than guessing. Confirm the priority of changes (must-have vs. nice-to-have) before starting the revision.
If the specific-element problem is the hard part — your client can't describe where they mean — Drafty gives them a link they open in a browser and click on the exact sentence, graphic, or section. The comment pins right there, no account needed. You see every note in one thread, reply in context, push a revision on the same link. Good for: design docs, PDFs, mockups, or anything you can share as a URL. Not a replacement for the brief or the consolidation step — but it removes the version-file problem entirely.
Open a live demoQuestions
- What is the best way to collect client feedback on a design?
- Send a written brief with specific questions before they look, walk them through the design with a short recording, then share a link they can annotate directly rather than emailing a file. Consolidate all notes before opening the design file to avoid acting on conflicting feedback.
- How do I get useful feedback instead of "I don't know, I'll know it when I see it"?
- Ask questions tied to the project goal rather than asking for opinions. "Does this match how you'd describe the product to a new customer?" gets a more useful answer than "what do you think?" Giving clients a framework before they look — not after — anchors their feedback on the right things.
- How do I avoid endless email chains when collecting design feedback?
- Share a single link rather than an email attachment. When clients download and re-send files, you accumulate versions. A shared review link keeps every comment on one artifact; replies stay in context and there's no competing file floating around.
- How do I consolidate feedback from multiple stakeholders?
- Nominate one point person on the client's team to collect and reconcile internal feedback before it comes to you. Two stakeholders giving contradictory notes in the same round is a scope and authority problem, not a design problem — resolve it with a question before starting the revision.
- What questions should I ask to collect client feedback?
- Useful questions: "Does the hierarchy match how you'd explain this verbally?", "Which section needs the most work?", "Does this feel right for the audience we discussed?", "Is there anything here that contradicts the brief?". Avoid yes/no questions and never ask "do you like it?" — that invites subjective reactions over useful direction.
- How do I collect client feedback without them needing an account or app?
- Share a link they can open in any browser and click on the element they mean. Tools that render your artifact as a reviewable web page — rather than requiring a download — let clients leave pinned comments with no software or signup.
Keep exploring
Stop emailing files back and forth.
Share one link. They comment on the exact spot — no account, always the current version.