How to Ask Clients for Design Feedback — Exact Prompts

You open the shared Figma link. Ten layers, three font weights, and one line from the client: 'Looks good—thoughts?'

That line ruins perfectly good progress. The real work is not convincing them you did a good job. It's getting an answer you can act on. This post teaches you how to ask clients for design feedback using exact prompts that force choices, surface tradeoffs, and reduce rounds.

Why precise prompts beat open questions

Open questions produce feelings. Specific prompts produce decisions. You're not doing therapy. You're asking somebody to evaluate a design, and most people don't enjoy swimming in design ambiguity. Give them a structure.

Vague feedback is a feature of poor questions, not bad clients.

How to ask clients for design feedback: exact prompts

These are the prompts you can paste into an email, Figma comment, PDF note, or ClientMarkup share link. Use them as-is, or tweak the labels.

• Concept stage (first impressions): 'On a scale of 1–5, how close is this to the direction you expected? 1 = completely off, 5 = ready to refine.'
• Priority check: 'If we had to ship one thing this round, what should it be: (A) CTA clarity, (B) hero image mood, (C) mobile layout?'
• Specific element choice: 'Which header works best? Pick A, B, or C and say one word why.'
• Content/sign-off point: 'Is the copy final? Reply: Yes — final, Edit — list line numbers, or Needs rewrite — send direction.'
• Visual tone: 'Would you prefer: (A) Minimal and airy, (B) Bold and textured, (C) Corporate and conservative?'
• Accessibility/usability: 'Any color or contrast concerns? Reply Yes/No. If Yes, indicate element or provide screenshot.'
• Bugs and interactions: 'Does the prototype behave like you expect? Reply: Works, Minor issues (list), Major issues (schedule call).'

Why these work: they limit the mental load. Choices force decisions. Scales give you a working number to compare across rounds. A single task reduces scope.

Templates for common stages

Use these exact messages depending on where you are.

1. Early concept (send with 2–3 screens)

Subject: Quick check — Homepage direction

Hi Sam,

Three quick asks:

1) On a scale of 1–5, how close is this to the direction you expected? 2) Which of these hero options do you prefer? A / B / C 3) Biggest concern if we proceed with your choice?

Please reply by Wednesday. If it's easier, pin a note on the screen and draw the change.

Thanks, [Your name]

2. Visual polish (pre-approval)

Subject: Visual polish — confirm assets

Hi Maya,

One task: confirm the header state and CTA.

• Do you prefer the rounded CTA or the square one? Reply Rounded / Square.
• On a 1–5 scale, how close is the header copy to final?

If you want a small change, please pin it on the design or use a short screen recording.

3. Final sign-off (ship-ready)

Subject: Final sign-off needed

Hi Alex,

Is this ready to publish? Reply with exactly one of the following: Approve, Minor edits (list below), or Reject (why).

By approving you'll confirm assets, copy, and responsive behavior for production.

How to send the questions (email, Figma, PDF, ClientMarkup)

Pick a single channel and stick to it. Don't scatter asks across email, Figma comments, and Slack—that's how feedback disappears. If you want precise annotations and a typed signature without forcing signups, use ClientMarkup. It lets clients pin, draw, and sign directly on the design link.

If you share Figma: attach a tiny note that repeats the three prompts in the file header and pin them to the relevant frame. For PDFs, put the questions in the cover email and ask them to annotate the PDF. For clients who love MS Paint markups, ask them to upload the screenshot and mark it; then transcribe the notes into your task tracker.

How to interpret answers

• A/B with one-word why: act on the winner, but keep the why. That word is your guardrail.
• Scale shifts: if the average jumps from 3 to 4, you know momentum; if it stays 3, you need a call.
• 'Minor edits' without specifics: follow up immediately with two clarifying questions or ask them to pin the exact spot.

Dealing with the classic 'I don't know' reply

Don't accept 'I don't know' as final. Convert it into something actionable: 'Which of these two is closer?' or 'Can you pin a single example from a competitor site?' The trick: reduce the choices to two. People can usually pick.

A quick checklist to attach to the review

• One-sentence goal for this round.
• Three targeted questions (use the templates above).
• Where to respond: single link or reply to this email.
• Deadline (48 hours for quick rounds).

You don't need clients to be design literate. You need them to choose. Make choosing easy.

Example: before vs after

Before: 'Any feedback?' After: 'On a 1–5 scale how close is this? Pick A/B/C for hero. If anything must change before Friday, pin it.'

You get specific answers. A quick note on timing: ask for a short deadline and move fast on the edits. Long pauses undo clarity.

If a client is still vague after all this, pick the best path, make the change, and document why. Show the next version and say, 'I chose X because you mentioned Y.' That's how you build trust and fewer rounds.

Want a place that lets clients pin their feedback and type a signature? Try ClientMarkup for link-based annotations and quick approvals.

Ask two targeted questions, not ten vague ones. Then ship the next version within 48 hours. Specific prompts shorten the loop and save you time — and your mood.