"You need to be more concise" — what they are actually reacting to

The feedback sounds like it is about volume. It almost never is.

People are not counting your words. They are noticing how long they waited. A three minute answer that opens with the conclusion reads as thorough. A forty second answer that arrives at the point last reads as rambling. Same word count, different verdict.

That is good news, because reordering is much easier than speaking less.

The four things that produce the feedback

You answer last. Someone asks a question and you begin with how you approached it. You are being rigorous, and it is being heard as evasion. By the time the answer arrives, the room has either guessed it or stopped listening.

You restate a point that already landed. You make the point, it registers, and you say it again in different words to be sure. The second version adds nothing and quietly signals that you did not trust the first one. This is the single most common cause and the easiest to remove.

You think out loud. You are working the problem in the room rather than presenting a conclusion from it. This is fine in a design discussion and expensive in a status update or a review, and most people do not switch modes between the two.

You add every caveat as you go. Each qualification is individually reasonable. Together they bury the sentence that mattered. The listener cannot tell which conditions are load-bearing and which are you being careful.

The mechanism nobody mentions

Here is why this is hard in a way that writing is not.

Speech has no revision loop. When you write, you produce a draft, read it back, see the paragraph that is doing nothing, and cut it. That loop is invisible and automatic and you use it constantly. In a meeting the loop does not exist. The first draft is the final draft, delivered at speed, while you are also tracking the room.

One engineer put it exactly right:

Talking is a stream of consciousness thing for me. Written communication is totally different, because I can write something, read it, refactor.

So the instruction “be more concise” is asking you to edit and speak simultaneously. Told that way, it is obviously hard. Told as “be more concise”, it sounds like something you should just be able to do, which is why it usually produces a month of self-consciousness and no change.

What to change, in order

One: answer in the first sentence. Whatever the question is, the first thing out of your mouth is the answer. Context second, and only if it is still needed. If you can only change one thing, change this one, because it fixes the perception on its own.

Two: stop after the point. Make it once. Then stop, and let the silence sit. The urge to fill it is the same urge that produced the second explanation. Resisting it looks like confidence, which is convenient, because it is also just a shorter answer.

Three: signpost when it genuinely is complicated. “Short answer, we should ship it. Three caveats if you want them.” You have given the headline, flagged the depth, and handed the room the choice. This is how you stay rigorous without making anyone wait.

Four: separate thinking from reporting. Decide before you speak which one you are doing. If you need to think out loud, say so, and people will follow you rather than waiting for a conclusion you have not reached.

How to tell whether it worked

This is the part that stalls people, and it is worth being blunt about.

You cannot assess this from inside your own head. Time spent talking feels shorter to the speaker than to everyone else. In the moment, the caveats feel necessary and the second explanation feels helpful. Every instinct you have about your own concision is measured with a broken instrument.

So use external evidence. Your share of talk time. How many sentences pass before your first complete answer. Whether the point appears twice. Those are countable in a transcript, and not knowable any other way.