How to stop rambling in meetings

You start answering a question and hear yourself searching for the point. Somewhere around the third sentence you find it, so you say it, then keep going, adding background nobody asked for, until you trail off with "so, yeah."

This article covers why that happens, a three-part shape for answering on the spot, a 60-second prep routine, and clean ways to stop once the point lands. Practice the structures in low-stakes meetings first, so they are available when the stakes go up.

The advice comes from Matt Abrahams, who has taught strategic communication at Stanford's Graduate School of Business for 25 years; Wes Kao, co-founder of Maven and altMBA, who coaches executives on communication; Tristan de Montebello, co-founder of the speaking school Ultraspeaking; and Lauren Ipsen, who recruits senior executives at Daversa Partners and General Catalyst.

Why you ramble in meetings

Rambling looks like a speaking problem. Usually something else is causing it, and three causes show up constantly.

You haven't decided what your point is

Wes Kao points out that the standard concision advice, "don't bury the lede", "cut to the chase", "bottom line up front", all assumes you already know what your point is. In her words: "You can't cut to the chase unless you know what the chase is." Her diagnosis is that long-winded answers come from unclear thinking, and word count is just the symptom (19:28 in the episode, which is embedded further down).

Real-time conversation already asks you to listen, process, decide, and speak at once. If you haven't picked the headline yet, you're doing all of that while everyone listens. Most rambling is just thinking out loud in front of other people.

You're performing instead of answering

Matt Abrahams sees a second cause: the pressure to sound impressive. Judging every sentence as you say it uses the same attention you need to actually form the answer. His fix has a name that lowers the stakes on its own.

Dull doesn't mean boring. It means trying to be useful instead of trying to sound brilliant. The phrasing can be ordinary, and the answer usually comes out better because you spent your attention on the question instead of on how you sound.

Silence feels like failure

Tristan de Montebello spent years training speakers at Ultraspeaking, and he treats filler words and rushed speech as symptoms rather than the problem itself.

People repeat themselves because stopping feels abrupt when you're the one talking. A pause feels much longer to you than to anyone listening. On a video call, look up while you gather your thoughts; looking down looks like you're checking your phone. If anxiety is what makes the silence feel dangerous, the guide to being more confident in meetings covers that side of the problem.

Answer, example, relevance

For questions you did not see coming, Abrahams teaches a three-part structure he calls ADD:

1. Answer. Lead with the bottom line: "I recommend moving the launch to next Thursday."
2. Detailed example. Give one fact or example that supports it: "Payment failures are running four times the normal rate."
3. Describe the relevance. Connect the evidence to the decision: "Three more days gives the team time to fix and retest checkout."

In the demo, Lenny asks how many students he has taught. Abrahams answers the real question underneath (his experience: 25 years, thousands of students), gives one example (he teaches in both academic and corporate settings), then states why it matters to the person asking (he can tailor material to their students). His warning: we assume listeners will connect the dots, and they usually don't. Connect them yourself.

Here is the difference in a launch meeting:

That last sentence matters. Offering more detail lets the group decide whether they want it, so you don't feel like you have to include everything up front. Then stop.

For updates and presentations rather than direct questions, Abrahams uses a sibling structure in the same episode (39:04): What, So what, Now what. Say the thing, why it matters, and what happens next.

Prepare the sentence you want them to remember

Kao is blunt about what actually fixes rambling, and it is not a delivery trick.

She is not talking about hours of prep. Even a couple of minutes before a weekly meeting makes a difference, and most people spend zero because they arrive still unwinding from the last call. De Montebello is specific about what those minutes should produce:

His claim, based on running this exercise with hundreds of speakers, is that people remember roughly one thing from a talk. Choose it on purpose. Before the meeting, spend 60 seconds on five questions:

1. If they remember one sentence tomorrow, what should it be?
2. What decision or action do I want?
3. What is the most likely objection?
4. Which example or number best answers that objection?
5. What is my first sentence?

Write the first sentence out and leave the rest as bullets. A fully scripted answer makes it harder to listen when the conversation moves.

Buy time before you answer

When someone asks you something and you haven't got the headline yet, do not start talking to fill the space. Take one breath and decide whether you understand what is being asked. A clarifying question is faster than a polished answer to the wrong problem. Lines that buy you time without sounding evasive:

• "Give me a moment to organize my answer."
• "Yes, with one important timing caveat."
• "Are you asking what happened, or what I recommend we do next?"
• "I see two issues. Let me take them one at a time."
• "I need to check the data before I answer confidently. My current hypothesis is..."

De Montebello's point from earlier applies here: when you pause on purpose, people just assume you're thinking. Look up, breathe, and begin when the first sentence is ready.

Put the headline first, keep context in reserve

In her 2022 conversation with Lenny, Kao describes how she structures written updates, and the same shape works out loud.

The logic: people who already agree get the gist and move on, and people who want your reasoning can keep reading, or keep asking. Spoken version: give the recommendation in one sentence, then let questions pull out the context. You keep the background; you just stop volunteering it.

One caveat from the same episode: a student of hers opened a customer email with "Bottom line:" and came across as aggressive. With your own team, lead hard with the point. With customers or executives you do not know well, add a sentence of warmth first.

Rehearse the stories you tell often

Kao has a test for her claim that clarity comes from preparation: think of your go-to story, the one where you know exactly when people will laugh. You tell it concisely because you have told it many times. Work anecdotes almost never get that practice, which is why the same project story wanders every time you tell it.

Lauren Ipsen sees the expensive version of this in executive searches.

The meeting version: the launch story, the outage story, the customer problem, the recommendation you keep making. Say each one out loud once before you need it, built around the decision:

1. Situation: one or two sentences of context.
2. Tension: the conflict, risk, or constraint.
3. Choice: what you decided and why.
4. Result: what changed.
5. Lesson: what you would repeat or change.

Unnecessary background becomes obvious the moment you have to say it in real time.

How long to talk, and when to stop

Concise does not mean short. Kao's counterpoint to all of the advice above:

A complex decision can deserve three minutes. The test is whether every part earns its place, and whether you stop when the question is answered, the relevance is clear, and everyone knows what happens next.

Kao's rule for agreement that arrives early, from the same episode (18:07): take the win. She used to keep presenting after executives had already said yes, and learned that more examples can only reopen a decision that has already been made. As Lenny puts it in the exchange, if you've sold them, stop talking.

Deliberate closing sentences make stopping easier:

• "That is why I recommend option B."
• "Those are the two risks I would solve before launch."
• "The decision I need today is whether to proceed."
• "That's the headline. Where would you like more detail?"

Frequently asked questions

Is rambling caused by anxiety?

Often, yes. Anxiety adds cognitive load and makes silence feel dangerous, so you talk to fill it. Preparation, a written opening sentence, and permission to pause all help. If nerves are the main driver, start with the meeting confidence guide, and consider coaching or clinical support if it persists.

How do I stop rambling in virtual meetings?

Keep a small note near the camera that says "answer, example, relevance, stop." Hide self-view if it distracts you. Look up while you think, so the pause looks deliberate instead of like you're reading something.

Will short answers make me sound abrupt?

Clear answers can still be warm. Add a brief transition such as "My recommendation is..." and invite questions after the headline. Kao's caveat applies too: with people who do not know you well, one sentence of warmth before the bottom line goes a long way.

The one-week plan