Being Right Is Not the Currency in Design

A client sends over the brief. It is detailed. It runs to two pages, and every line of it is trying to help.

The button should be bigger. The logo should move to the centre. The call to action needs to pop more. The sign-up form belongs at the top of the page.

Nowhere in those two pages is there a problem. There is only a list of solutions, written by someone who was never hired to produce solutions and does not realise that is what they have done.

The brief that skipped a step

Somewhere behind that document there is a real problem. Probably something like this: the website doesn't convert, and I don't understand why.

A problem statement that names the gap between what is happening and what should be happening, and it leaves open the question of what to do about it. That open question is the entire reason a designer was hired.

But problem statements are uncomfortable to sit with. They admit uncertainty. So the client keeps thinking, and thinking turns into solving, and by the time the brief is written the discomfort has been resolved — into a bigger button, a centred logo, a form moved up the page. Something that now only needs execution and little to no trust towards the executioner.

The tell is always the level of detail. Nobody specifies a button size while describing a problem. The moment the sentences turn prescriptive, the brief has crossed from description into instruction. Every one of those instructions is a decision that is closing off the space where the work was supposed to happen.

And the client has no idea they have done it. They believe they have been helpful. They have been thorough, specific, clear — all the things a difficult client is not. From where they sit, this is a good brief.

Which is why the cost stays invisible on both sides. The designer never reaches the best answer, and the client never learns what they didn't get.

Why correcting them loses

The instinct is to fix it on the spot.

"That won't work. Button size doesn't drive conversion. What you actually need is —"

Everything after "that won't work" is wasted, because the client stopped listening at the third word. They have just been corrected in their own meeting, and now they are defending a position rather than thinking alongside you.

There is a longer-term cost too. Correcting a client teaches them to stop offering. Next time, they skip the reasoning and hand over the orders.

But the real problem is structural, and it has nothing to do with tone.

Design, to someone who hires designers rather than practises it, is a subjective matter. The evidence that would settle an argument about button placement is thin, contested, or absent. So the moment you contradict the instruction, you have not started a debate about facts. You have started a debate about taste.

And a debate about taste, with the person paying for the work, is a debate that cannot be won. Not because the argument is weak. Because the ground is wrong. On subjective terrain, the person with the budget is right by default, and no amount of being correct changes that arithmetic.

You can win every point and still deliver the bigger button.

Being right is not the currency here. Influence is.

Go underneath, not against

The move is not to meet the instruction. It is to travel under it.

The instruction is the surface of something. Behind "make the button twice the size and centre it" sits a chain of reasoning the client has never said out loud — an observation, a worry, a thing someone told them once, a number they saw last quarter. That chain is where the real brief is.

So ask. Not once, but down through the layers: Why that? What makes you think that's the issue? Why would that change things? Applying genuine curiosity rather than the tone of cross-examination, will usually reach the source.

This takes time. It is slower than nodding and executing. But the design at the end of it is better, and the client has been part of building it rather than being talked out of something.

Two things can happen when you arrive at the source.

Sometimes you find that the client was right. They had a reason. They saw something real, expressed it as a solution because that was the only vocabulary available to them, and the bigger button is genuinely the answer. This happens more often than designers like to admit, and the only way to find out is to have asked.

More often, you find a hunch — an assumption that has been sitting unexamined behind the certainty.

Ask them to bet on it

Annie Duke, in Thinking in Bets, makes a distinction worth borrowing. Chess is a game of complete information, where a correct move exists and can be found. Poker is not. Poker is a game of decisions made under uncertainty, and good poker players think in probabilities rather than certainties.

Design decisions are poker, not chess. Nearly all of them are bets on incomplete information.

So once you have reached the source, make the bet explicit. Would you put money on doubling that button lifting conversion?

Watch what changes. An instruction costs nothing to hold. A bet has something at stake. The claim that felt obvious a moment ago now has to be priced, and very few people will wager on a hunch once it has been named as one.

Nothing has been contradicted. No one has been made wrong. The client has simply been asked how confident they actually are, and has audited their own certainty on your behalf. The doubt is handed over, not imposed.

That is when the door opens for the alternative — and the alternative should arrive as a question, not a verdict.

"Do you think we'd lose anything if, instead of doubling it, we fixed the contrast and shifted it left?"

Open-ended, low-stakes, easy to say yes to. It invites a reaction, not a defence.

The frame is the work

None of this is manipulation. If it were, the client would eventually notice, and the trust would be gone.

It is a refusal to accept a losing frame. The instruction-versus-counter-instruction conversation is one the designer cannot win, and it is offered by default at the start of nearly every project. Declining it, and replacing it with genuine inquiry, is the single highest-leverage move available before any work begins.

The best solution is rarely the one that arrives in the brief. It is also rarely the one the designer had in mind before the conversation started.

It is the one that neither party could have reached alone — which is why the conversation, not the correction, is the work.