29 August 2026
The person who dominates a meeting almost never thinks they're doing it — they think they're the one moving things forward. Fixing it isn't feedback you deliver later; it's structure you impose right now, in the meeting itself: going round the table on purpose, naming the next speaker, and saying the timebox out loud before anyone starts talking.
A meeting with no explicit turn order defaults to whoever is fastest, loudest, or most senior. That's not a character trait working against you — it's an absence of rule filling itself in with whatever's available. Confidence and rank both fill a vacuum faster than a good idea does, which is why the person with the most airtime is so often not the person with the most useful thing to say.
Treat it as a design problem and the fix stops being personal. You're not correcting someone's behavior; you're replacing an undefined default with a defined one, the same way you'd fix a race condition by adding a lock instead of asking the threads to be more considerate.
Say it plainly: "Let's go round — Priya, then Tom, then you." A go-around works because it turns speaking from something you have to win into something you're owed. Nobody has to interrupt to get in; the interruption has already been pre-authorized for them by the order you named.
It also caps the dominant talker without singling them out. Their turn ends when the order moves on, not when you decide they've said enough — which is a much easier thing for both of you to live with.
"Tom, you flagged pricing risk on this before — what's your read now?" is a different move than "anyone else want to add something?" The open question competes with the loudest voice in the room and loses. The named question has no competition; it's a direct handoff, and the person named almost always answers it, because being asked by name carries a social obligation that an open floor doesn't.
"Two minutes on this, then we move" — said before the discussion starts, not after it's run long — turns the clock into the authority instead of you. When you cut someone off at minute four, you're not being rude; you're enforcing a rule everyone in the room already agreed to when you stated it out loud.
This matters more than it sounds like it should. A facilitator who interrupts on judgment gets read as opinionated or impatient. A facilitator who interrupts on a stated timebox gets read as fair, even by the person being cut off.
Most advice on this quietly assumes the dominant talker is a peer. It falls apart the moment it's your manager, or your manager's manager, because you can't cut off someone who signs your review the same way you'd cut off a colleague.
The techniques don't change — the sequencing does. Get the timebox agreed before the meeting, not asserted during it: "can I hold us to two minutes each on this one, including you?" asked over Slack the day before gets a yes almost every time, and that yes is what you enforce later, not your own judgment in the room. In the meeting, address the process, never the person: "we're at the two-minute mark we agreed on" lands as neutral; "you're talking too much" does not, regardless of how true it is. And if you genuinely can't interrupt a senior voice live, ask them first in the go-around rather than last — most seniority-driven monologues happen because the senior person is filling silence, not because they're waiting to dominate; give them the floor early and briefly, and there's often nothing left for them to fill later.
A pattern across meetings is easier to raise than a single instance, and much harder to argue with. If your notes or transcript capture who spoke and for how long, you can point to a shape over three or four meetings — "you've had the majority of airtime in the last three planning calls" — rather than relitigating one afternoon. AVAY keeps a transcript per speaker and lets you search across past meetings, so that pattern is something you can pull up rather than something you have to remember correctly.
What it can't do is fix the meeting for you. It won't interrupt the person mid-sentence or decide the timebox on your behalf — the facilitation moves above still have to be said out loud, by a person, in real time.
| What it fixes | Social cost to say | Works on the most senior person in the room | |
|---|---|---|---|
| Go-around | Uneven turn-taking generally | Low — feels procedural, not personal | Yes, if seniority speaks in its assigned slot |
| Naming the quiet person | One person's silence, not the talker's volume | Low | Yes — doesn't touch the dominant speaker at all |
| Timeboxing out loud | Long monologues on one topic | Medium — you're enforcing a limit live | Only if agreed before the meeting, not during it |
| Pre-agreed process comment | Repeated pattern across meetings | Medium — requires a private ask in advance | Yes — built for exactly this case |
Get the timebox agreed in a message before the meeting, not asserted live — "can I hold us to two minutes each, including you?" almost always gets a yes over Slack. In the room, address the process you both agreed to, not their behavior: "we're at the two-minute mark" is enforceable; "you're talking too much" is not, no matter how accurate it is.
Interrupting a person is rude; interrupting on a rule you stated at the start isn't, because everyone in the room already agreed to it. The rudeness people feel usually comes from an ungrounded interruption based on your judgment in the moment, not from enforcing a timebox you announced out loud before anyone started talking.
Say the structure explicitly rather than relying on body language you can't see well over video — "let's go round the grid, starting with Priya" works whether or not you can tell someone's about to jump in. A tool that shows who's spoken and for how long, like AVAY's live notes, replaces the visual cue you'd normally get from a raised hand or a leaning-forward posture in person.
That usually means the question was too open. "Anything to add?" invites a shrug; "what's the risk on the timeline specifically?" invites an answer. Narrow the question when you name the person, and the go-around stops producing filler.
It works better there, not worse, because the alternative — open floor with ten people — collapses into whoever speaks first almost every time. Timebox per agenda item and go round only the people directly affected by that item; the rest can be asked in writing afterward.
You don't fix a dominant talker by talking to them about it — you fix them by changing what the room is structured to reward, one stated timebox and one named handoff at a time.
AVAY is a video meeting platform that transcribes the call itself — no bot joins, because there is nothing to join. Start one at avay.ai, read how each part works in the documentation, or see what it costs.