"The client is always wrong about design" is one of those lines that only ever gets said in the room designers share with each other — never the room with the client in it. Say it in a design Slack channel and everyone nods. Say it in a review call and you've probably just lost the account.

That gap is the actual subject here. Not whether clients are wrong about design — they often are, in specific and describable ways — but why the people paid to know better routinely let the wrong call stand without a fight. The usual answer is some version of "designers should explain their reasoning better." That's true and also not the point. Most designers already know how to explain a decision. The question worth asking is why, knowing the reasoning, they frequently choose not to use it.

The Myth Does One Job: It Protects the Designer, Not the Deck

"The client is always wrong" survives as a phrase because it's a clean, blameless explanation for something that's actually more complicated — a designer watching a weaker version of a slide get approved and not objecting. It's easier to file that under "clients don't get design" than under "I saw the problem and said nothing." The first version costs nothing. The second one requires admitting a choice was made, and that the choice wasn't really about the client's taste at all.

None of this means client instincts are secretly always right — plenty of pushback really is just unexamined personal preference dressed up as feedback. But treating every override as proof the client "doesn't get it" lets a designer skip the harder question: given that I disagreed, why did I go along with it anyway?

What Actually Keeps the Correction From Happening

Organizational researchers have spent a fair amount of effort on a version of this exact problem, just framed around employees and managers instead of designers and clients. Harvard Business School's James Detert and Amy Edmondson studied what makes people speak up about a problem they've noticed versus stay quiet, and found the deciding factor wasn't confidence in being right — it was a person's sense of how much power they held relative to whoever they'd be correcting, and whether that person seemed genuinely open to hearing it. Low perceived power plus low perceived openness reliably produced silence, even among people who were certain of their position.

Swap "manager" for "client" and the mechanism barely changes. A designer on a per-project invoice, hoping for a repeat engagement or a referral, is not operating from a position of structural power in that relationship — the client can walk, the designer usually can't easily replace the income. Voicing disagreement isn't free in that arrangement. It's a bet against a client who may or may not react well, made by the person with the weaker hand. Staying quiet isn't a failure of nerve so much as a rational read of who's holding more leverage in the conversation.

The Cost-Benefit Math Nobody Says Out Loud

Here's the part that rarely gets acknowledged: for a single project, the math usually favors silence. Winning the argument gets you a better slide that maybe three people in the client's building will ever consciously register. Losing it — even just losing it socially, by coming across as difficult — can cost the retainer, the referral, or simply the ease of the next call. One of those outcomes is visible and immediate. The other is a marginal improvement to a document most of its audience will forget by Friday. Framed that way, the "professional" choice and the "conflict-avoidant" choice point in the same direction, which is exactly why it's so hard to tell them apart from the inside.

This is where the standard advice — "just explain your reasoning clearly" — quietly assumes something it shouldn't: that the client is undecided and waiting to be persuaded by a good argument. That works when there's already enough trust in the relationship that a client is willing to be wrong out loud in front of the designer. It does very little in a one-off, transactional engagement where the client came in with a fixed opinion and is looking for execution, not counsel. Reasoning changes minds that are open to changing. It doesn't manufacture that openness where none exists.

Sometimes the "Wrong" Call Is a Business Signal the Designer Misread as Taste

It's worth being honest about the other half of this, because it cuts the other way. Not every override is a client failing to appreciate good design — some of them are a client correctly sensing that a slide answers a different question than the one the room is going to ask. A slide can be well-designed and still not do its job, and a client pushing back on something that looks clean but doesn't actually support the argument being made isn't wrong about design — they're right about persuasion, even if they'd describe the objection as "I just don't like it." Designers who assume every disagreement is an aesthetics problem will occasionally overrule a client who is, in fact, catching something real.

The distinction worth training yourself to notice: taste objections tend to be vague ("something feels off"), while function objections, even when phrased vaguely, usually resolve into a specific complaint once you ask a follow-up question — "who's going to be reading this slide on a screen versus printed," or "does this need to work without me in the room." One of those is worth holding your ground on. The other usually isn't.

A Narrower Way to Disagree That Doesn't Require Winning the Whole Argument

Given the actual incentives at play, blanket advice to "push back more" is asking designers to absorb more risk than the relationship usually rewards. A narrower version works better: instead of arguing the aesthetic point, name the mechanism it's protecting against, and let the client weigh that specific trade-off rather than your general taste.

"I'd keep this at two colors" invites a taste argument you might lose. "A third accent here means two different things on the slide are both fighting for the same half-second of attention" describes a cost the client can actually evaluate against their own goals — the underlying issue is rarely the number of colors itself, it's how many separate jobs each one is doing. That reframe doesn't guarantee the client agrees. But it moves the conversation from "my judgment versus yours" to "here's a specific cost, is it worth paying" — a much smaller, much more winnable disagreement, and one that doesn't require the client to concede you're the more sophisticated party in the room.

It also helps to pick the fights with an actual budget in mind. Removing something from a deck is always a harder sell than adding it, because cutting requires someone to stand behind the decision out loud — so save that particular fight for the choice that genuinely changes whether the deck works, not the one that's just aesthetically preferable to you.

One thing that quietly reduces how often this fight needs to happen at all: starting from a structure where the contentious calls — hierarchy, color roles, type pairing — were already made deliberately before the client ever saw a draft. A template built around a working set of those decisions doesn't remove taste disagreements entirely, but it does mean fewer of them are live at review time, because the mechanism the client would be arguing with was decided upstream rather than defended live in the room.

Next time a call goes the way you didn't want it to, it's worth sitting with a more specific question than "was the client wrong about design." Ask instead whether you actually made the case, in terms the client could weigh against their own stakes — or whether, somewhere in that thirty seconds before you agreed, you'd already done the math on what disagreeing would cost you.