How to Translate Vague Client Feedback Into Design Decisions

“Can you make it pop?”

“Something feels off, but I can’t put my finger on it.”

“It’s almost there, but it needs more… I don’t know, energy?”

If you’ve taken client feedback for more than a year, you’ve heard versions of all three. Most designers hear them and feel a small flicker of irritation. The client doesn’t know what they want. They’re being lazy. Why can’t they just give a clear note?

That reaction is wrong.

The client is telling you something real. They’ve spotted a problem on the design that’s bothering them, and they don’t have the vocabulary to describe it. That’s not lazy. That’s how every non-designer experiences design. The skill of freelance web design isn’t taking precise notes and executing them. It’s translating fuzzy reactions into actionable decisions.

Here’s how to do it.

The translation framework

Every vague piece of client feedback maps to a specific design problem. The trick is knowing the map.

”Make it pop”

What they’re saying: I can’t tell what’s important on this page. My eye doesn’t land anywhere.

What’s actually wrong: You have a visual hierarchy problem. Everything has roughly the same weight, so nothing stands out as the primary element.

The fix: Establish dominant contrast. One element on the page needs to be visually louder than the others — through color, size, weight, spacing, or all four. The hero headline. The primary CTA. A signature image. Pick one. Make it scream while the rest whispers.

The client doesn’t need to know any of this. They just need to look at the next version and feel their eye lock onto the right element. That’s “pop."

"Something feels off”

What they’re saying: This page is harder to read than it should be, and I can’t pinpoint why.

What’s actually wrong: There’s a friction in either alignment, spacing rhythm, or proportion. The eye is doing extra work to parse the layout.

The fix: Check the basics. Are all your elements aligned to a clear grid, or is everything slightly off? Is your spacing rhythm consistent (e.g., all section padding is 80px, all element gaps are 24px, all card padding is 20px) or is it inconsistent? Are your image proportions creating awkward shapes?

90% of the time, “feels off” is a spacing problem. Audit every section. Make every spacing decision intentional. Most “off” feelings disappear when the page has rhythm.

”It needs more energy”

What they’re saying: This feels static. There’s no movement or surprise.

What’s actually wrong: The layout is too predictable or too monotonous. Every section has the same structure. Every visual element sits flat on the page.

The fix: Vary the rhythm. If three sections in a row have a left-text-right-image layout, change one. Introduce an off-grid element. Add a tilted shape, an overlapping image, an asymmetric arrangement. Use scale variation — make one element noticeably bigger than the rest.

Animation is the lazy answer to “needs more energy.” It rarely helps. Composition variety usually does.

”Can we make the logo bigger?”

What they’re saying: I don’t feel like my brand is present enough on the page.

What’s actually wrong: Either the brand colors aren’t being used consistently, or the page doesn’t reflect the brand’s personality, or there’s no brand recall mechanism beyond the logo.

The fix: Don’t make the logo bigger. Instead, reinforce the brand throughout the page. Use the brand color as the primary CTA color. Use the brand font for headlines. Repeat a signature visual motif. Add a small footer credit. Make the page feel like the brand without needing a 200px logo.

Then show the client. They’ll feel the brand presence without realizing why, and the logo can stay the appropriate size.

”Make it more professional”

What they’re saying: This feels too casual, too cheap, or too amateurish for our business.

What’s actually wrong: Usually one or more of: weak typography, inconsistent grid, low-quality stock images, busy or noisy backgrounds, too many decorative elements.

The fix: Strip back. Remove anything that’s decorative without function. Upgrade the typography to a serious typeface with tight tracking. Use whitespace generously. Replace stock photos with original photography or no photography. Reduce the color palette to two or three colors.

“Professional” is almost always “less stuff, executed better."

"It needs to feel more friendly”

What they’re saying: This feels cold, clinical, or intimidating. The visitor won’t feel welcomed.

What’s actually wrong: Usually warm cues are missing. Warm cues include: human faces, rounded corners, warmer color temperatures, hand-drawn elements, conversational copy, casual photography.

The fix: Add one or two warm elements. A human photo on the homepage. A rounded button radius. A friendly accent color. A microcopy line that sounds like a person, not a department. You don’t need to redesign the whole thing — small warmth signals go a long way.

”Make it look more premium”

What they’re saying: This doesn’t justify our pricing or position us as high-end.

What’s actually wrong: Usually the design lacks one or more of the premium signals: editorial typography, generous whitespace, high-quality photography, restraint, custom illustrations or motifs.

The fix: Whitespace, whitespace, whitespace. Premium design breathes. Replace any stock photography with custom imagery or none. Use one or two typefaces with confidence. Restrain the color palette. Remove any element that doesn’t justify its presence.

Premium is rarely about adding. It’s about removing everything that isn’t necessary.

”I don’t like the color”

What they’re saying: One specific color is creating an emotional reaction that doesn’t match the brand intent.

What’s actually wrong: This is usually exactly what they said. But sometimes “I don’t like the green” means “this entire palette doesn’t work,” and you need to know which one.

The fix: Ask one clarifying question. “Do you mean this specific shade of green, or the role green plays in the design overall?” Their answer tells you whether to adjust the shade or rework the palette.

If it’s the shade, try two alternatives in the same hue family. If it’s the palette, step back further and ask what feeling they want the colors to evoke. Then translate that into color choices.

How to ask for clarification without seeming clueless

When a client gives you fuzzy feedback, you have two options. You can interpret it yourself based on the translation framework above. Or you can ask for clarification.

Don’t ask “what do you mean?” That puts the burden back on the client to articulate something they can’t articulate.

Instead, ask leading questions that help them spot what’s bothering them:

• “When you say ‘make it pop,’ do you mean the headline isn’t grabbing your attention, or the CTA isn’t standing out enough?”
• “When you say ‘something feels off,’ is it more the layout structure, or the spacing, or the way elements relate to each other?”
• “When you say ‘more energy,’ do you want it to feel faster, more dynamic, or more colorful?”

Each question gives the client two or three concrete options. They pick the closest one. You have a starting point.

The feedback you should always push back on

Most vague feedback should be translated and incorporated. Some shouldn’t.

If a client says “I want to add a video background to the hero” or “let’s add an autoplay carousel” or “can we put a chatbot here,” these aren’t fuzzy feedback. They’re specific feature requests. And most of them make the site worse.

For these, push back with reasoning, not with “no.”

“Video backgrounds reduce conversion because they slow load time on mobile and distract from the primary CTA. We could use a still hero image that captures the same energy without the performance cost. Want me to show you what that would look like?”

You’re not refusing. You’re presenting a better-informed option. The client almost always accepts when the reasoning is sound.

The unspoken contract of design feedback

When a client hires a designer, they’re hiring a translator. They’re paying you to take their fuzzy mental image and turn it into a website that works.

If you treat their feedback as inputs to a literal interpretation machine, the result is a design that doesn’t work but technically follows instructions. The client is unhappy. They blame the design. You blame the brief.

If you treat their feedback as symptoms of a real underlying problem — and you diagnose the problem and solve it — the result is a design that actually works. The client is happy. They don’t know why. They just feel like they hired the right person.

That’s the job.

Translating fuzzy feedback isn’t a chore you suffer through. It’s the core skill that separates good designers from great ones.

---

debrieft turns the messy intake conversation into a structured brief, so you start every project with the client’s real problem already mapped out. Your client gets a portal. You get a dashboard. Both in sync. Try it free at debrieft.app