Decoding What Client Feedback Really Means

“Make it pop” has become shorthand for everything designers find frustrating about client feedback: vague language, questionable taste and a request that seems to arrive without any understanding of the work already done. It is easy to laugh at because the phrase sounds like an instruction while offering almost nothing a designer can act on.

It is also usually an honest attempt to describe a real discomfort. The client may not know whether the problem is hierarchy, contrast, tone or the fact that the most important message appears too late. They know only that the page does not yet produce the response they expected. “Make it pop” is not a solution. It is evidence that something remains unresolved.

The designer's job is not to obey the phrase literally or dismiss it as unsophisticated. It is to translate the discomfort into a question specific enough that both sides can evaluate the next decision.

Feedback usually describes a symptom

Clients experience design as readers before they learn to discuss it as makers. They notice effects: the page feels cold, the logo seems small, the presentation lacks energy. Designers tend to answer with causes: colour temperature, negative space, scale, rhythm. Trouble begins when either side assumes its vocabulary is the work itself.

“The logo needs to be bigger” may mean the brand is not recognisable quickly enough. Increasing the logo is one possible response, but so is reducing nearby competition, changing its position or making the surrounding system more distinctive. If the designer treats the note as a measurement, the logo grows and the original problem may remain.

The same is true of “it feels empty.” Sometimes the page lacks information. More often, the empty space has no visible purpose because hierarchy elsewhere is weak. Filling every gap can make the page busier without making it feel more resolved. The note is useful once it becomes a conversation about what the reader should understand in that space.

This translation requires curiosity at the moment defensiveness feels more natural. A designer has already made dozens of connected decisions, and a short comment can appear to ignore all of them. The client sees a result without that history. Neither view is complete.

The most productive response is often a small sequence of questions:

• Where did your eye go first, and where did you expect it to go?
• What feels absent: information, emphasis or personality?
• Is this concern about the intended audience or your own preference?
• Which existing example feels closer, and what specifically changes there?
• What would become easier for the reader if this revision worked?

These questions are not a way to force the client to use design terminology. They are a way to find the decision hidden underneath their language.

Translate, test and show the trade-off

Once the concern is clearer, a designer should return with more than a corrected file. The revision needs to make the translation visible. “We increased contrast around the primary message rather than enlarging every element” explains both what changed and why the literal request was not followed.

Showing alternatives can help, provided the alternatives represent meaningful choices rather than one good design placed beside two punishments. A restrained option might preserve the current hierarchy. A more expressive option might introduce stronger colour and image scale. The comparison gives the client something concrete to react to and exposes the cost of each direction.

The trade-off is the part designers most often leave implicit. If the logo becomes larger, less room remains for the campaign message. If every product receives equal emphasis, none can lead. If the interface feels more playful, it may also feel less formal. Naming these exchanges turns subjective preference into a decision about priorities.

A short decision note helps when feedback passes through several people. It records the concern in the client's language, the interpretation agreed together and the change being tested. This prevents the next review from reopening the original ambiguity as if no conversation happened. It also lets a stakeholder disagree with the interpretation before a designer spends hours resolving the wrong problem.

The note need not become administrative ceremony. Three sentences attached to the proof are usually enough. Its value is that it separates what was heard from what was built, making both available for review.

There are limits to interpretation. Some feedback is contradictory, some is driven by internal politics and some asks the design to solve a disagreement the organisation has avoided. No arrangement of type can decide which audience matters most if the client has not decided. In those moments, the designer's responsibility is to name the unresolved choice rather than endlessly revise its surface.

It is equally important not to romanticise every vague note as hidden wisdom. Clients can be wrong. Designers can defend an unsuccessful choice because they remember how much work it took. The aim is not to assign authority permanently to either side. It is to create a method through which the work can be tested against what it needs to accomplish.

Good feedback conversations change the object and the vocabulary around it. Over time, a client begins to say that the hierarchy feels flat instead of asking for more pop. A designer learns that “too quiet” from this particular team often means the main idea is arriving too late. The shared language becomes part of the design system, as useful as a spacing scale or set of type styles.

Every note is a question in disguise, but not always the question written on the page. Decoding it is not extra diplomacy added around the real design work. It is how the real problem becomes visible enough to design.