Client Feedback in English: Clarify a Vague Brief With Mad Men
A client says, “Make it more premium.” Or “I’m not feeling it.” Or “Can you make it pop?” You nod, leave the call, and realize you still have no idea what to change. That is not a vocabulary problem. It is a brief-decoding problem.
The safest move is not to guess faster. Use four moves: VAGUE → VALUE → CONSTRAINT → CONFIRM.
VALUE: find the business or audience outcome behind the reaction.
CONSTRAINT: surface what must stay, what cannot happen, and who decides.
CONFIRM: restate the brief in concrete terms before another round of work.
The four-question client-feedback diagnostic
| Stage | Ask yourself | Useful English |
|---|---|---|
| VAGUE | What word or reaction is too broad to execute? | “What specifically isn’t working for you?” |
| VALUE | What result does the client actually want? | “What are you hoping this changes?” |
| CONSTRAINT | What is fixed: budget, audience, evidence, deadline, brand, approval? | “Is that a hard requirement or a preference?” |
| CONFIRM | Can both sides agree on one concrete brief? | “Let me check I’ve got this right…” |
VAGUE: a reaction is not yet a brief
One of the most dangerous feedback phrases is positive-sounding but empty. In the episode, a client reaction lands as:
That's very interesting.
That may mean “I like it,” “I’m surprised,” “keep talking,” “I’m unconvinced,” or simply “I need a second.” Do not treat it as approval.
“When you say interesting, which part feels strongest to you?”
“Is there anything you would want changed before we develop this direction?”
“Should I read that as positive interest, or do you still have concerns?”
A harsher reaction can be equally vague. The episode also gives:
you could do better than this.
The sentence communicates dissatisfaction, but not the criterion. Your job is to turn it into one.
VALUE: find the real job underneath the request
Clients often describe a solution when they actually need an outcome. “Use a coupon.” “Make the homepage darker.” “Add AI.” Before you execute the proposed solution, find out what success means.
In the client meeting, one simple question cuts toward motive:
why did you come here?
That is the deeper move: why are we doing this project at all?
The useful business pressure emerges elsewhere in the meeting:
we just had our lowest sales year ever.
Now the brief is no longer “do something innovative.” The real problem is commercial performance. That changes the questions you should ask.
“What are you hoping this changes for the business?”
“What should the customer think or do differently?”
“What matters most here: conversion, trust, awareness, retention, or something else?”
“What would make this feel successful three months after launch?”
CONSTRAINT: discover what cannot move
A brief becomes usable only when you know its boundaries. Budget is one obvious limit; legal claims, brand position, channel, deadline, and stakeholder approval can matter just as much.
The episode gives a compact way to express a hard limitation:
But our hands are tied.
That idiom means the speaker has little or no freedom to act because of an outside constraint. In real client work, do not stop at the idiom. Name the constraint.
“We can’t make that claim because legal has not approved it.”
“We can change the layout, but the launch date is fixed.”
“We can test a larger media plan, but it would require a higher budget.”
If evidence matters, ask for it directly. One scene does exactly that:
There's no proof.
You do not need to sound combative. Try: “What evidence are we using for that assumption?” or “Do we have data that supports this direction?”
CONFIRM: do not leave the room with two different briefs
A disagreement can feel productive while both sides are still imagining different projects. Before you finish, summarize the brief in plain English.
A useful move in the episode is to slow an escalating conversation:
Let's take it a little slower.
That is excellent meeting English when the discussion is moving faster than the shared understanding.
“Let me check I’ve got this right.”
“So the priority is attracting higher-value customers, not increasing coupon response. Correct?”
“If we keep the brand position but change the campaign idea, are we on the right track?”
“Before we make another version, can we agree on these three requirements?”
You can also acknowledge before clarifying. The episode gives:
I see your point.
That does not mean you agree with everything. It means you have heard the objection. A strong sequence is: acknowledge → clarify → summarize → propose a next step.
Bad feedback vs actionable feedback
| Vague feedback | Better follow-up | What you are trying to learn |
|---|---|---|
| “Make it more premium.” | “Do you mean visual style, audience, price perception, or tone?” | The exact dimension to change. |
| “It needs more energy.” | “Which moment feels slow, and what should the audience feel instead?” | Where the problem is and the desired reaction. |
| “I don’t like the homepage.” | “Is the issue trust, navigation, hierarchy, or visual style?” | The failure criterion. |
| “Use more AI.” | “What user problem should AI solve here?” | The outcome behind the requested feature. |
| “Make it like Competitor X.” | “Which quality are you responding to: simplicity, tone, structure, or positioning?” | The transferable principle, not the imitation. |
| “This audience won’t respond.” | “What evidence or past result are we basing that on?” | The basis of the assumption. |
Three client scenarios: turn the fog into a brief
Website redesign
You: “When you say premium, do you mean the visual style, the type of customer it signals to, or the price perception?”
Client: “Mostly trust. We sell to enterprise buyers.”
You: “Got it. So the priority is enterprise trust. Which elements are fixed—brand colors, existing copy, or page structure?”
Client: “Colors stay. Everything else can change.”
You: “Great. I’ll develop one direction that keeps the colors but improves hierarchy, proof, and enterprise credibility. I’ll show the reasoning with the next version.”
Ad campaign
You: “What do you want the audience to feel or do that they are not doing now?”
Client: “Remember us. We look like every competitor.”
You: “So distinctiveness matters more than broad appeal. Is there anything we absolutely cannot change?”
Client: “The product claim and legal wording stay.”
You: “Understood. I’ll push the concept and visual identity while keeping those claims fixed.”
Product feature
You: “Possibly. What user problem should it solve?”
Client: “Users don’t know what to do next.”
You: “So the real goal is guidance, not AI itself. Is response speed or explainability more important?”
Client: “Explainability.”
You: “Then I’ll compare an AI-assisted option with a simpler rule-based option against that goal before we commit.”
Vague-feedback decoding worksheet
| Write this down | Your answer |
|---|---|
| The vague phrase or reaction | ________________________ |
| The likely business/audience value | ________________________ |
| The biggest unknown | ________________________ |
| Hard constraints | ________________________ |
| Who has final approval? | ________________________ |
| Your one-sentence confirmed brief | ________________________ |
| Your next concrete step | ________________________ |
Practice: decode the feedback before proposing a solution
Client: “I want it to feel younger.” What should you ask first?
Model answer: Ask what “younger” is supposed to achieve. For example: “Are you trying to reach a younger audience, modernize the visual style, or change how established customers perceive the brand?” Do not redesign until the value is clear.
Client: “We need this everywhere.” What is the missing constraint?
Model answer: Channel scope. Ask where “everywhere” actually means: paid social, email, retail, TV, web, print, or all of them. Then ask which channels are essential and which are optional.
Client: “This copy doesn’t work.” Turn it into actionable feedback.
Model answer: “What specifically isn’t working—the message, tone, clarity, evidence, or call to action? Which part should stay?”
Client: “We love it.” What still needs confirming?
Model answer: Whether this is actual approval, what must remain unchanged, who else needs to review it, and what the next deliverable is. Positive emotion is not the same as a signed-off brief.
A short role-play you can reuse
You: “I understand. What specifically feels wrong about it?”
Client: “It feels too mass-market.”
You: “Is the concern mainly the audience signal or the visual execution?”
Client: “Audience signal. We need to attract fewer but higher-value buyers.”
You: “That helps. What can’t change?”
Client: “The offer and price.”
You: “So the priority is premium positioning for higher-value buyers while keeping the offer and price fixed. I’ll revise the message and creative direction around that and bring back two options. Does that match what you mean?”
How to disagree without overpromising
Clarifying feedback does not mean obeying every request. It also does not mean performing certainty you do not have.
Clarify: “What result are you trying to protect?”
Summarize: “So the requirement is X, while Y must stay fixed.”
Propose: “I can test two options against that. I can’t promise the outcome yet, but I can show which option best fits the agreed criteria.”
When you need to correct an interpretation, a small phrase can keep the conversation moving:
Not exactly.
Follow it with the distinction: “Not exactly. The issue isn’t the visual style; it’s that the current version does not explain the value quickly enough.”
Before you leave the meeting
Practice the feedback move with FunFluen
When you watch a client or agency exchange in FunFluen, pause before the reply and predict the function: goal, constraint, objection, or confirmation? Then reveal the subtitle, save the useful chunk, and rebuild the same move for a different project. The point is not to memorize Mad Men dialogue. It is to make vague professional English actionable.
Explore more media-based language-learning guides in FunFluen Learn.