Address Repeated Interruptions During Team Meetings

Repeated interruptions in a team meeting rarely fix themselves. If you let the pattern continue, the person being cut off learns their input matters less, and the person doing the interrupting learns that speed beats listening. A private, timely conversation resets both expectations without turning the issue into a spectacle in front of the group.

Why This Conversation Goes Wrong

Most managers stumble here for one of two reasons. Either they wait too long and raise it only after frustration builds, or they open with a judgment about the person's character instead of a description of what happened. Saying someone is impatient or does not respect their colleagues turns a fixable habit into a personality fight. The employee gets defensive, and the actual behavior never gets named clearly enough to change.

The other common error is treating the interruption as purely a confidence or ego problem. Sometimes the person interrupting is trying to flag a real risk before the group moves on, and they do not trust that raising it later will get attention. If you only address the interruption and ignore the underlying urgency, you fix the symptom and leave the cause in place. The behavior returns at the next meeting under a different topic.

How to Prepare Before You Talk

Before you sit down with the employee, collect two or three specific instances. Name the meeting, the moment, and what happened, not your interpretation of it. A note like "cut off Jordan twice during the vendor update on Tuesday" gives you something to work with. A note like "dominates every discussion" does not, because it hands the employee nothing concrete to change.

Check your own role in the room too. If you run the meeting and never redirect the conversation back to the person who got cut off, you have been reinforcing the pattern every week. Decide now whether you also need a visible meeting norm, such as a rule that speakers finish their point before anyone responds, so the individual conversation lands as part of a fair standard rather than a rule aimed at one person.

Think through what you want by the end of the talk. You want the employee to leave with one specific action for the next meeting, not a general promise to be better about it. A specific action might be writing the point down and raising it during a pause, or waiting for the facilitator to open the floor.

What to Say

Open with the observation, not a label. State what you saw, name the effect it had on the group, and stop talking. Give the employee room to respond before you propose a fix, since the answer tells you whether this is a habit, a trust issue with the process, or something else.

Manager Imani said, "In Tuesday's planning meeting, you spoke over Jordan twice while she described the vendor delay, and Marcus stopped before he got his question out. I want the team to hear a full point before we react to it." Devon answered, "I was worried we would run out of time to deal with it." Imani replied, "Bring the time concern in right after the person finishes. Could you write it down and say 'I have a timing question' once there is a pause?" Devon said, "Yes. I can also check whether someone is actually done before I jump in."

Notice what that exchange does. Imani names the pattern with two concrete examples, states the effect on the group, and offers a specific replacement behavior instead of just asking Devon to stop. Devon gets a chance to explain the motivation, which turns out to be legitimate, and the talk ends with an action both people can check for next time.

If Devon pushes back and says the meeting moves too slowly to wait, treat that as useful information rather than an excuse. It means the team may need a clearer way to flag urgent items, not just a rule about interrupting less. You can raise that with the group separately while still holding Devon to the same standard as everyone else in the room.

Mistakes to Avoid

Do not raise this in the meeting itself or in front of other attendees. Calling someone out live adds embarrassment on top of the correction and makes the employee defend their reputation instead of hearing you. Take it to a private conversation within a day or two of the meeting, while the details are still fresh for both of you.

Do not soften the message into vague feedback like "try to let others finish." That gives the employee nothing to act on and nothing you can check later. Name the meeting, the person, and the moment.

Do not skip the follow up. A single conversation rarely changes a habit built up over many meetings. If you raise it once and never mention it again, the employee has no way to know whether the new approach is working or whether you even noticed the change.

Do not apply the standard to only one person while letting others interrupt freely. Employees notice when a rule is enforced selectively, and it undermines the fairness of the whole conversation. If more than one person on the team interrupts, address the pattern with the group and set a shared norm alongside the individual talk.

How to Practice and Score This Conversation

This is a conversation that goes better with rehearsal, because the instinct under pressure is to either avoid it or open with a label. Run through it with a practice partner or with a tool built for this kind of rehearsal, and pay attention to three things. Did you describe the behavior without judging the person. Did you let them explain before you assigned a fix. Did the conversation end with one specific action, not a vague promise.

DealSpeak lets you rehearse this exact scenario against an AI counterpart that reacts the way a real employee might, including pushback about time pressure or a defensive first response. You can review the transcript afterward and check whether you stayed on the observation, invited context, and landed on a concrete next step. The scoring flags moments where feedback drifted into character judgment, which is the single most common way this conversation goes sideways.

This same discipline, describing what happened, naming the effect, and agreeing on a specific behavior, applies well beyond meeting interruptions. The HR and Leadership practice conversations library covers a wide range of manager conversations built on the same structure. If you want to see it applied to a different kind of accountability talk, look at how to Discuss a Missed Deadline After a Dependency Changedor how to Give Feedback on Missed Handoff Details With a Specific Work Example when the issue is a dropped detail rather than a meeting habit.

Interruptions are a small behavior with a large effect on how safe people feel raising ideas in your meetings. Name the pattern early, give the employee something specific to try, and check back after the next meeting to see if it worked. Handled this way, the conversation strengthens the team norm instead of just correcting one person.