Handling Client Feedback without Losing Your Mind

Handling Client Feedback without Losing Your Mind

"Can I make the logo bigger?" "I don't like the blue, can I make it pop more?" "It feels a bit empty here."

For developers and designers, vague client feedback is a source of immense frustration. It feels like an arbitary attack on my logic and hard work. I spent hours aligning the grid, and now the client wants to break it because "it doesn't feel right."

But usually, the problem isn't the client. The problem is the Translation Layer.

The "Why" behind the "What"

Clients are not designers. They lack the vocabulary to describe what is wrong. So, they speak in Solutions ("Make the logo bigger"), even though they are actually feeling Problems ("I am worried people won't remember my brand").

If you just do exactly what they ask (make the logo huge), the site looks ugly, the balance is ruined, and ironically, the client still isn't happy because the underlying anxiety hasn't been resolved.

The Strategy: The "Five Whys"

My strategy is to never accept a solution at face value. I ask "Why?" repeatedly to dig down to the root cause.

Client: "Make the logo bigger." Me: "I can do that. But can I ask why you feel it needs to be bigger?" Client: "Because the header feels empty." Me: "Interesting. Is it that the logo is too small, or that the space around it feels unbalanced?" Client: "Yeah, it just feels like something is missing on the right side."

The Real Fix: The issue wasn't the logo size at all; it was the Whitespace balance in the header.

The Solution: I don't resize the logo (which would look tacky). Instead, I add a subtle background pattern or move the navigation links to balance the visual weight.

The client is happy because their problem is solved. The design stays clean because I controlled the solution.

As a consultant, my job isn't to be a pair of hands executing orders. It is to be a translator. I translate their business anxiety into technical excellence.

Best,

Gerasimos Makris Founder of g-makris.com AI Web Developer | Double Master's in MBA & FinTech and Blockchain

Tech Glossary & Concepts

• Translation Layer: The skill of converting non-technical business requirements into technical specifications.
• Stakeholder: Anyone who has an interest or concern in an organization or project (clients, bosses, users).
• Whitespace (Negative Space): The empty space between and around elements of a page. It is not "wasted" space; it is a critical element of design that improves readability and focus.
• Root Cause Analysis: A method of problem solving used for identifying the root causes of faults or problems.