Design feedback examples: good vs bad (with rewrites)

You're staring at an email from a client: 'Make it pop.' That's one of the worst design feedback examples you can get. It says nothing about what 'pop' means, who you're optimizing for, or what to change in Figma, a PDF, or an exported JPG.

Bad feedback costs time. It creates 2–3 rounds of vague revisions, awkward back-and-forth, and a final design that's optimized for the loudest voice rather than the user. The fix is not 'be nicer'—it's specific, measurable, and contextual. Below are concrete design feedback examples (bad and rewritten), plus a short method you can copy into your next reply.

Design feedback examples: good vs bad rewrites

Here are real situations you see every week. For each: the bad feedback, why it fails, and a rewrite you can paste into an email or a Figma comment.

1) Header on a marketing page (desktop)

Bad: 'The header image feels off.'

Why it fails: No clue what ‘off’ means — scale? crop? tone? It leaves the designer guessing.

Good: 'The hero image feels cluttered and competes with the headline. Goal: headline readable at 34px on 1366×768 without scrolling. Try a tighter crop on the product so face is centered, and reduce overlay opacity to 50%. Priority: high for launch.'

Why this works: Problem + measurable goal + specific fix + priority.

2) Mobile CTA

Bad: 'Make the CTA button more visible.'

Why it fails: 'More visible' is subjective and platform-specific — on mobile that often means tap target size and contrast.

Good: 'On iPhone SE, the primary CTA appears quite small. Goal: meet 44px tap target and WCAG AA contrast against the background. Option: increase padding to 12px top/bottom, change CTA color to #4F6EF7, or move the CTA above the fold on product pages. Priority: critical for conversions.'

3) Typography in a PDF handout (print)

Bad: 'The text looks weird.'

Why it fails: Could be leading, weight, size, column width — and if it's print, pixel sizes don’t help.

Good: 'In the 8.5×11 PDF, body text at 9pt is tight on the second paragraph. Goal: improve readability for print; change body to 10.5pt with 14pt leading and limit column width to 55–65 characters. If that breaks layout, reduce image size on page 2 by 8%.'

4) Color choice

Bad: 'That blue doesn't feel right.'

Why it fails: 'Feels' is personal. Designers need objectives — brand, accessibility, emotional cue.

Good: 'The blue on the signup button reads too cool compared to our brand swatches. We want friendlier warmth. Target: use a blue within 5% hue of brand swatch B2, or try #4F6EF7 at 90% saturation. Must keep AA contrast against white. Priority: medium.'

5) Interaction / microcopy

Bad: 'This interaction is clunky.'

Why it fails: No mention of where or how it's clumsy.

Good: 'When you tap the filter on mobile, the drawer takes 600ms to open and there's no loading state; users might think taps didn't register. Goal: open within 200–300ms or add a skeleton/loader if data is slow; keep animation under 300ms. If backend is slow, add a disabled state after first tap.'

6) Client markup from MS Paint (classic)

Bad: 'Make the logo bigger — roughly here.' (scribble arrow)

Why it fails: Size 'bigger' is ambiguous; scribbles don't show scale or alignment.

Good: 'Move the logo into the left gutter, align to 24px from the page edge and scale to 120px wide (matching the header compact layout). Attached screenshot with a red box where it should sit.'

7) Copy conflict

Bad: 'I don't like this headline.'

Why it fails: Subjective and unhelpful.

Good: 'Headline currently reads "Get things done." It's vague for our B2B audience. Goal: communicate ROI in 6–8 words. Try "Save 3 hours per week with X" or "Scale onboarding without extra hires." Priority: high for homepage.'

Good feedback is built like a spec: measurable, replicable, and tied to an outcome.

How to write your own actionable feedback (the 4-line formula)

Use this mini-template when replying to a design email or pinning a comment:

• Problem — what you see, as specifically as possible.
• Why it matters — conversion, readability, brand, accessibility.
• Success criteria — a measurable target, a reference, or a hard constraint.
• Priority — low/medium/high and any deadline.

Example: 'Problem: hero CTA blends into the image and is unreadable on mobile. Why: hurts conversions. Success: CTA needs 4.5:1 contrast and 44px tap target. Priority: high for Wednesday launch.'

When clients or stakeholders don't have the time to format feedback, ask for a screenshot with pins, or a 20–30s screen recording narrating the issue. Time-stamped video or pin-and-draw annotations remove the guesswork. If you want a simple place to collect that kind of comment-and-signoff, drop things into ClientMarkup and let people pin, draw, and sign without creating more accounts.

Quick anti-patterns to avoid

• Don't use mood adjectives alone: 'sleeker', 'friendlier', 'busier.' Pair them with what should change.
• Don't pile five unrelated asks into one bullet — it creates a laundry list of partial fixes.
• Don't mandate implementation details unless you're limiting scope: if you say 'use a gradient at 15deg,' explain why other options are off the table.

Give people something to act on. Designers will love you for it — or at least stop asking clarifying questions on Friday afternoon.

Next time you read 'make it pop,' reply with a one-line rewrite using the 4-line formula. It saves hours and produces work that actually hits the goal.