Don't Brood Over It. Just Pick Up the Phone and Have a Conversation

I noticed it over a colleague's shoulder. She was writing an email — a long one. Paragraph after paragraph, and still going. I asked her what it was about. She showed me the design, and the thing she was arguing over: the placement of a button. A subjective call, dressed up as a UX question, and the client wanted it one way while she wanted it another.

She was building her case in writing. Proving her point.

That is the moment this whole piece comes from — because the length of the email was the problem. You do not write three careful paragraphs to someone you are about to understand. You write them to someone you have already decided to out-argue. The moment she started typing, she had positioned herself in defense. And defending yourself is the one posture from which you cannot understand the client — which is the only thing that ever resolves a subjective disagreement.

The whole thing could have been shorter, warmer, and finished, if she had picked up the phone.

The Medium Chooses Itself

Watch how it happens in the everyday version. You share the Figma file. The comments land — forty-eight of them. Some trivial, a margin or a colour. A few load-bearing, touching the logic of the thing. And the instinct kicks in: answer them, resolve them, clear the board. Comment by comment, because the goal has quietly become to get through them.

Nobody decided to handle a subtle disagreement inside forty-eight threaded comments. Nobody weighed call, meet, or type and chose type. The medium chose itself, one reply at a time. That is a decision — and like most decisions that shape design outcomes, it got made by default, in the space before anyone was paying attention. But this channel is not neutral. It sets how much of the truth is allowed to travel.

What Text Actually Carries

When people communicate feelings, only a sliver of the meaning lives in the words. The tone carries more. The face carries the most. The rule gets quoted as seven, thirty-eight, fifty-five, and the skeptics are right that it was never a universal law of all information. But it holds precisely where feelings and attitudes are in play — and especially where the words and the tone might quietly contradict each other.

So ask the question that decides everything for our work: when are feelings not in play in design?

"I don't like it" is feeling. "I'm not sure about this" is doubt. Whether the client believes you actually understood them is the subtext of every review — and none of it is in the words. Text is the single channel that throws away everything except the words. It is the worst possible medium for the one kind of conversation design actually requires. A button that is really a matter of taste will never be settled in writing, because it was never a logic problem to begin with.

Read the Package, Not the Tasks

The instinct to clear the board treats forty-eight comments as forty-eight tasks. They are not a to-do list. They are one message, with a shape and a weight. Half might genuinely resolve in seconds. A few are load-bearing. Before you touch any of them, sit with the whole set and read it as a package: what is the client really telling you? Where is the real friction? The tricky ones are rarely about what they literally say. Only once you have read the weight do you have something worth acting on.

Why It Doesn't Feel Like a Call

Calling someone over a single comment feels absurd. So you never call for one — and the forty-eight never trigger a call either, because each one, judged alone, is too small to justify picking up the phone. The weight lives in the package but instinct judges the comments one at a time.

Reframe it. Don't call about the comment. Call about the round — because inside it there are a few that genuinely need a conversation, and it is faster and better to talk them through than to type past each other for two days. That framing gives you the standing to dial. And when you dial, bring a structure: lead with the critical ones, the load-bearing few. Then name the second and third tier briefly — here is what I'll simply do with those.

The Phone Is Already in Your Hand

The phone is always with you now. A comment thread is not faster than that — it only feels faster, because sending is quick. But the reply might sit for five days while the client's attention is elsewhere, and by the time it comes back you have moved on and must reload the whole problem in your head. It is latency dressed up as efficiency, and it manufactures its own frustration. A two-minute call collapses the five days to nothing, and hands you more precise, more usable information than any written reply ever will. Even if they don't pick up. There is a good chance they will call you back.

A Call Is a Doorway

This is the part that matters most. A written thread closes things down — it narrows, it flattens, it ends in a row of resolved checkmarks. A call opens things up. You have room to move inside it, to hear the hesitation, to follow the thread the client didn't quite put into words. And a call can do the one thing text never will: pull the other person toward a real conversation — a proper working session — where the actual decision work gets done. Text is a dead end. A call is a doorway.

It is true that picking up the phone feels less natural than it used to, for some more than others. That is simply where we are. It doesn't change the arithmetic. If you can have the conversation by voice, it is faster, it is more human — and you have far more room to move than any email will give you.

That long email was never going to work. Not because the argument was weak, but because the argument was the problem. Don't brood over the comments. Don't stew over the thread, rehearsing replies in your head. The instinct to win it in text is the instinct to give away the ninety-three percent that carries the truth.

Pick up the phone. Really.