How to Give Design Feedback to Clients — Coach Them

You open your inbox. Subject: 'Make it pop.' Body: three flattened screenshots with red circles drawn in MS Paint.

You know what 'make it pop' means. It means the client likes the direction but can’t express which levers to pull. It also means you’re about to play therapist, detective, and production manager for an afternoon.

This is about how to give design feedback to clients — from your side. You won't teach them design school. You will teach them to be useful.

How to give design feedback to clients without the 'Make it pop' emails

Start by assuming the feedback is human, not malicious. Clients rarely mean to waste your time. They lack vocabulary and context. Your job is to build a small bridge.

Here’s a practical frame you can hand to any client in 30 seconds. Make it the default:

• Outcome: What should the user do? (e.g., 'Book a demo', 'Find pricing')
• Problem: What is stopping that outcome? ('CTA is too low contrast', 'pricing page feels crowded')
• Suggestion: One specific change or example (color hex, font weight, layout swap)
• Priority: Critical / Nice-to-have / Future

Give them this as a short, copy-paste email. Repeat it until they stop writing 'Make it pop.'

If feedback is a list of feelings, translate it. Ask: which of these three things do you want us to change — copy, hierarchy, or color? One at a time.

Scripts that get replies (copy these)

If the client writes vague feedback, reply with a targeted question. Keep it simple:

• Client: 'The hero feels flat.'
• You: 'Do you mean the photo, the headline hierarchy, or the contrast of the CTA? Pick one and I’ll adjust it this afternoon.'

Or when they send a PDF with red circles:

• You: 'Thanks — can you pin the exact element and tell me whether this is device-specific? If you prefer, record a quick screen note (30–90s). Either works for me.'

Most clients will pick the easiest option. That’s fine.

Turn vague phrases into tasks

Common offender phrases: 'Make it pop', 'Looks weird', 'Not quite right'. Your system for each:

1. Ask a single clarifying question. Keep it one sentence. 2. Offer two options. (Less visual noise / bigger headline, warmer photo / cooler photo.) 3. Ask them to pick or hand you permission to choose.

Two options is a muscle. People can pick between two things. They can't pick between twelve.

Tools that save you hours

Figma comments are great when clients live in Figma. But they rarely do. If your client can’t open Figma, don't force it. Use a tool they can click into without accounts.

• Share a live link that accepts pins and typed approvals. (This cuts email chains.)
• Offer short screen-recording options — 45–90 seconds, spoken notes. A client will say more in 30 seconds than in three paragraphs of email.
• When you must deal with PDFs: ask for page and element numbers, or convert into a link that accepts pins.

If you don’t have a dedicated client-facing markup in your stack, try ClientMarkup for quick share links, pin comments, and sign-off. It fixes the basic problem: clients need a low-friction place to be specific.

How to prioritize feedback like a pro

Not all feedback is equal. You need a simple rule to decide what to act on immediately:

• If it blocks a user task or breaks accessibility, it’s high priority.
• If it’s an aesthetic preference that doesn’t affect conversion, it’s low.
• If it’s a content change, keep it separate from visual changes; assign to copy or content owner.

Write this rule into your kickoff emails. If a client flags 'make the CTA red' and it's just taste, ask: 'Does this change improve conversions or accessibility?'

Scripts for approvals and scope control

Get explicit sign-off. An approval should be a typed line: 'I approve version 3 for production.' Not a passive 'looks good'.

Make extra rounds billable in the scope doc. Put it in the kickoff: 'Two feedback rounds included; additional rounds $X/day.' Clients complain less when a fee is attached.

Log approvals visibly in your project doc. Timestamped feedback links or a short Loom with a 'this is approved' line are gold.

Example 1: Figma-dependent client

You send a Figma file and get a single comment: 'Header too big.'

Your move: add a comment on the same frame: 'Do you mean H1 size (48px→42px) or spacing above the hero (64px→48px)? Pick one and I’ll push a change.'

They pick one. You change it. Done. Short, trackable.

Example 2: The PDF + red circle crowd

You get three flattened images with red circles and no context.

Reply: 'Thanks. Could you pin each issue and tell me: (1) device (mobile/desktop), (2) what you'd like to change, (3) priority. If you prefer, record a 60s screen note.' Drop a link to a markup tool they can open without an account.

Most will either pin or record. You win.

Teach once, save weeks

The first two projects with a new client will be clumsy. Teach the frame. Stick to scripts. Make the preferred feedback path the easiest path: click a link, pin a comment, record a note.

You will hear resistance: 'This takes time.' Reply: 'It takes 60 seconds now and saves us 3–4 emails later.' That math is persuasive.

If a client still insists on MS Paint circles, send the template and the one-click link anyway. People follow a simple form.

If you're tired of translating feelings into tickets, put the work into the process, not the argument. Train them to use the right muscles. The project finishes faster, and you do better work with less headache.