What "Be More Concise" Really Means for Executives

"Sorry, so is that a yes?" It might seem like a polite question, but it’s also quietly devastating. It usually comes with a forced semi-smile, the kind you can tell implies “I have no idea what you mean.”

Here's how you got there.

You're in a boardroom, or on a call with investors. It doesn't really matter which. The room is senior and the clock is running. Someone asks you something simple. “Are we going to hit the numbers this quarter?”

You know the answer. You've known it for two weeks. You could recite it in your sleep, and some nights you probably have.

What comes out instead is "So, to give a bit of context, as you know, in Q2 we had the migration, and the vendor situation was more complicated than we expected, and then in July we made the decision to..."

Somewhere around the word July, you feel it. Someone glances down at their laptop. Someone else nods, but it's the nod people give a flight attendant during the safety demonstration. Polite. Patient. Elsewhere.

And then the question. "Sorry, so is that a yes?"

If your stomach dropped a little just now, I want you to know two things. You're in extraordinarily good company. And this has almost nothing to do with your English.

The Meeting After the Meeting

The uncomfortable part isn't just the moment itself. It's also the conversation you have with yourself in the elevator afterward.

Because that's where the verdict gets delivered, and it's always the same one. “It's my English. If I just worked harder on my English, this wouldn't keep happening.”

So you prepare more. You rehearse the whole explanation, every moving part, every exception you can see coming from a mile away. You walk into the next meeting with the full case built brick by brick, because surely if you show them everything, they'll finally see that you're not just capable. You're rigorous.

The room wanted a decision. You handed it a dissertation (with footnotes).

The Smartest People in the Room Do This the Most

I coach executive communication for a living, so I realize it sounds a little strange when I tell you that over-explaining isn't a language problem.

It feels like one, because it happens more in English than in your first language. So of course you blame your English. But the people I see do this most are almost never the ones with the least English. They're actually the ones with the most expertise.

Think about it, the more deeply you understand your business, the more there is to explain. When you can see every moving part, leaving one out feels irresponsible. Almost like lying by omission, so you include it. All of it.

You're not unclear. You're thorough, too thorough. The trouble is that the room wasn't asking for thoroughness. It was asking for judgment.

One founder I worked with, a genuinely brilliant engineer, came to me completely convinced that English was his problem. In our first session, I asked him the question every investor asks. So what does your company do?

Several minutes later, I knew a great deal about his technical architecture. Every word was accurate and his message was grammatically correct. I still didn't know what his company did, or why I should care. He was answering how it works when the listener needed to know why it matters, and by the time he reached the part that mattered, an investor's attention would have quietly left the building.

His English was fine. His packaging was the gap.

Two Correct Rules, One Very Confusing Room

There's a cultural layer underneath all of this, and it's where I see a lot of guilt and confusion that doesn't belong to the person carrying it.

In many cultures, context is how you earn trust. You don't walk into a room and drop a conclusion on the table. You show people how you got there, because that's what careful, serious people do. It's a form of respect.

Then you carry that instinct into a room running on a different code, usually American, usually low-context, and the exact same professionalism reads as something else. Slow. Evasive. Like you're warming up to bad news or don’t really know the content.

You didn't do anything wrong. Two perfectly good rules just collided in the middle of your meeting. And you're already code-switching all day long, between languages, between accents, between the version of you that writes emails and the version that presents to the board. This is one more switch, and nobody ever handed you the manual.

You Need To Be More Concise

“Could you be more concise?” This is usually the moment someone says it. And what you hear is "say less."

So you cut words. And now you sound clipped and still somehow unclear, which feels deeply inauthentic.

Here's what almost nobody explains. When you’re asked to be more concise, they rarely mean shorter. They mean sooner.

You can speak for three minutes and sound beautifully concise if the answer arrives in your first ten seconds. You can speak for forty seconds and sound like you're rambling if the answer only shows up at the very end. At that level, conciseness is a question of order not length.

The First-Sentence Test

Before you answer anything that matters, ask yourself one question. If they only heard my first sentence, what would they walk away with?

Your first sentence. Not your first few minutes.

Picture the person across the table with a notebook open. What line ends up on that page? That's your opening. Everything else is available on request.

Now let's rewind to the boardroom. “Are we going to hit the numbers this quarter?”

Same you, same knowledge, same English. "Mostly, yes. Revenue is on track globally. The one real risk is the Mexico launch, which could slip by about three weeks. I'm happy to walk you through why."

Nothing about your English level changed. What changed is that you decided what mattered, and that decision is the expertise. Leaving things out isn't the opposite of being thorough. It's what thoroughness looks like once it's finished its homework.

Then Comes the Hard Part

Stop.

You give a clean answer, and there's a beat of silence. In another language, two seconds of silence can feel like an eternity. Your brain red flags it immediately. “Uh oh, they didn't get it, quick, add more.” So you add more, and now you're back in the dissertation, just with a fresh layer of nerves on top.

I'd like you to hear that silence differently. In a senior room, a pause after your answer is almost never confusion. It's processing. It's the sound of your point landing.

So let your voice drop at the end of the sentence, and then actually stop. A rising tone at the end tells the room you're not sure you're done. A falling one tells them you are.

And if there's more worth sharing, offer it. Don't impose it. "I can walk you through the numbers if that's useful," lands completely differently than deciding on their behalf that they need all of it.

What They Were Really Asking

The next time someone asks you a simple question in a senior room, remember what's underneath it. They're not testing your vocabulary or wanting to see how eloquent you are. They're asking for your judgment so a decision can be made efficiently and effectively.

Your expertise was never the problem. It just kept arriving too late.

Get Exclusive Insights

I go deeper into this pattern, the layers underneath it and the tools that actually untangle it on this week's episode of Leadership English. Listen to the full episode here.

And if you want the frameworks I build for moments exactly like this, plus the insights I don't share anywhere else, join the Leadership English Insiders today.