How long should an answer in a meeting be?

There is no correct number of seconds, and chasing one produces clipped answers that are worse than long ones. The useful test is where the conclusion sits: if someone interrupted you halfway, would they already have the answer? Lead with it, then give the reasoning to whoever still wants it.

Is talking a lot the same as talking too much?

No, and conflating them is why a lot of advice here backfires. Volume is about share of the conversation; conciseness is about the shape of a single answer. You can hold the floor for most of a meeting and be perfectly concise, or say very little and bury every point.

Does this apply if English is my second language?

It gets sharper. Assembling reasoning out loud is harder in a second language, so answers run longer and the conclusion arrives later. The structural fix — conclusion first — costs less fluency than trying to speak faster, which is the thing most people attempt instead.

How to be more concise in meetings

Nobody sets out to give a ninety-second answer. It happens because you are assembling the reasoning out loud, and the conclusion arrives when the assembly is finished. The listener, meanwhile, has been waiting for the number since the first sentence.

In your report: Conciseness · your three longest answers, with a shorter version of each

Lead with the answer, then explain

If someone asks what the downtime will be, the first thing out of your mouth should be the number. Everything else is support, and support is optional — the listener will ask if they want it.

I think maybe we could possibly need a window. Since two months we are working on it, and the performance looks fine, so we would need about four hours on a Sunday night.

About four hours, on a Sunday night. Happy to go into why.

One idea per turn

A long answer is usually three answers wearing a coat. If you catch yourself saying “and also”, that is a second turn trying to escape. Stop, let them respond, and see whether the second point is still needed.

Cut the runway

Phrases like “so, basically, what I would say is” carry no information. They buy thinking time, which is legitimate — but silence buys the same time and costs nothing.

So, basically, I think what I would say is that the API is the dependency.

The API is the dependency.

Conciseness is not brevity

The goal is not a shorter meeting. It is that the person listening gets the thing they asked for first, and the reasoning second. A four-minute answer that starts with the conclusion is fine. A twenty-second answer that buries it is not.

Your report finds your three longest answers and writes the shorter version using your own words and your own facts, so you can see exactly what was load-bearing and what was runway.

Common questions

How long should an answer in a meeting be?: There is no correct number of seconds, and chasing one produces clipped answers that are worse than long ones. The useful test is where the conclusion sits: if someone interrupted you halfway, would they already have the answer? Lead with it, then give the reasoning to whoever still wants it.
Is talking a lot the same as talking too much?: No, and conflating them is why a lot of advice here backfires. Volume is about share of the conversation; conciseness is about the shape of a single answer. You can hold the floor for most of a meeting and be perfectly concise, or say very little and bury every point.
Does this apply if English is my second language?: It gets sharper. Assembling reasoning out loud is harder in a second language, so answers run longer and the conclusion arrives later. The structural fix — conclusion first — costs less fluency than trying to speak faster, which is the thing most people attempt instead.

See which of these is yours

Paste a transcript from a real meeting and find out, rather than guessing.

Check a real meeting

No account, and nothing is stored.