Feedback·August 28, 2026·4 min read

How to Tell Someone They Talk Too Much in Meetings

The exact phrasing to tell a colleague they're dominating meetings — framed around airtime and group impact, not personality, so it doesn't land as an attack.

How to Tell Someone They Talk Too Much in Meetings

Say it in terms of airtime and group impact, not personality: "In the last few meetings, I've noticed you're taking up a lot of the airtime, and I think it's crowding out other people's input." That sentence works because it names a pattern, not a trait. Calling someone "dominating" or "a talker" attacks who they are. Naming airtime attacks a habit — one they can actually change.

This is also why almost nobody delivers this feedback. It sits in a strange zone: too minor to escalate to HR, too awkward to say out loud, so it just gets absorbed. People roll their eyes in the follow-up Slack thread. They start scheduling smaller meetings just to avoid the one person. Resentment builds quietly for months, and the person causing it has no idea, because nobody has told them.

Why this feedback almost never gets delivered

Three things kill it before it starts. First, it feels petty — "you talk too much" sounds like a complaint you'd make about a sibling, not a colleague. Second, the person is usually good at their job and enthusiastic, which makes the feedback feel like punishing engagement. Third, there's no clean moment to say it. You can't interrupt them mid-meeting without it becoming a public correction, and bringing it up later feels like you've been quietly building a case against them.

The result is that this feedback almost always gets skipped, and skipped feedback doesn't disappear — it turns into eye-rolls, side-channel complaints, and a manager eventually hearing "yeah, everyone knows Dave runs long" as old news he should've caught months ago. If you're the one who noticed it first, you're also the one best positioned to say something before it hardens into team-wide resentment.

The framing that doesn't read as an attack

The move is to talk about the meeting's function, not their character. You're not saying "you talk too much." You're saying "the meeting isn't working the way it should, and here's the mechanism." That shifts the conversation from judgment to logistics — something you can problem-solve together instead of something they have to defend.

Concretely, that means:

  • Use the word "airtime," not "talking." Airtime is a resource, like meeting time or budget — it's neutral and quantifiable. "Talking too much" is a judgment about them as a person.
  • Name the effect on the group, not on you. "I've noticed a few people go quiet when this happens" lands very differently than "it annoys me when you do this."
  • Bring a specific, recent example. "In yesterday's planning meeting, you had the floor for probably fifteen of the thirty minutes" is concrete and undeniable. "You always talk too much" is a vague accusation they'll instinctively push back on.
  • Ask a question instead of only stating a conclusion. "Do you think you're getting more airtime than makes sense in these meetings?" invites them into the diagnosis instead of handing them a verdict.

Here's what that sounds like in a real 1:1:

"Hey, can I flag something about our team meetings? I've noticed you tend to take a big chunk of the airtime — probably more than you realize — and I think it's making some of the quieter people on the team check out. I don't think you're doing it on purpose, but I wanted to name it because I think the meetings would run better with more voices in them. Does that land, or does it feel off to you?"

Notice what's missing: no "you always," no character judgment, no comparison to other people by name. It's specific, it's about function, and it ends with a genuine question, not a lecture.

What to say if they ask "how much is too much?"

This question trips people up because they haven't thought past the opening line. Have an answer ready, and make it about proportion, not a stopwatch. A useful anchor: "If there are six people in the meeting, no one person should be taking more than a third of the floor time on a regular basis — otherwise it's not really a group conversation anymore." That's a rule of thumb, not a rigid quota, and it gives them something concrete to self-monitor against.

You can also hand them a practical fix instead of just a number: "One thing that helps is pausing after you make a point and asking someone else what they think, instead of building on it yourself." That reframes the ask from "talk less" (vague, hard to act on) to "build in a handoff" (specific, repeatable, doable in the very next meeting).

If they get defensive and say "well, I just have more to contribute," don't argue the point — redirect to the group outcome: "Maybe so, and I'm not saying your input isn't valuable. I'm saying the meeting works better when it's not one-directional, and right now it's landing that way." Keep bringing it back to the mechanism, not the personality.

This is a conversation most people get exactly one shot at before it curdles into "everyone secretly thinks this about you and no one's told you." The words matter more than usual, because the wrong opener turns a fixable habit into a defensive standoff. Practice in ConvoForge before the real conversation — you can run it against an AI that pushes back the way a defensive colleague would, adjust your phrasing based on how it lands, and walk into the actual 1:1 already knowing which version of this works.

Practice this in 5 minutes

Challenge Directly, Care Personally

In flat, remote teams, indirect feedback gets misread. Directness paired with warmth is the only thing that actually changes behavior.

Open lesson #37
Published August 28, 2026 · More articles →