Ask a Colleague to Stop Interrupting You

This template covers a weekly project meeting where a peer keeps cutting you off while you are trying to give an update. The interruption is repeated across multiple meetings, so the learner has to address a pattern rather than a one-off slip. It is designed for moments when you need to stay calm, name the behavior, and keep the meeting moving. The goal is to practice a real in-the-moment correction, not a vague conflict conversation.

Use it for individual contributors, team leads, or anyone who needs to speak up when a colleague talks over them. It is especially useful for people who tend to wait until after the meeting and then avoid the issue. The scenario works well for learners practicing assertiveness, boundary-setting, and concise workplace communication. It is also useful for managers who want to coach employees on peer-to-peer feedback.

A few short attempts are usually enough to build a usable response, but it helps to revisit the scenario whenever the learner struggles with interruption patterns. Because the template is based on a repeated meeting behavior, it is a good fit for deliberate practice: one attempt to try a direct approach, another to refine tone, and another to tighten the request. The point is to rehearse a response that can be used immediately in a real meeting. Repetition matters more than long sessions.

This template trains the learner to respond in the moment, which is often when the interruptions have the biggest impact. Waiting until later can make the issue feel less concrete and can let the pattern continue. The roleplay helps the learner practice naming the interruption clearly, explaining the effect on their ability to contribute, and asking for a specific change. That combination is harder to do well than a generic follow-up message.

Yes. You can adjust Taylor’s temperament to be more defensive, more unaware, or more receptive depending on the learner’s needs. You can also tune the opening line, the level of pushback, and the tone expectations to match a more formal or more casual team culture. The core structure should stay the same: identify the interruption, describe the impact, and make a clear request. That keeps the practice realistic while still flexible.

Learners often stay too vague, soften the message so much that the interruption is never named, or jump straight to blame. Another common mistake is making a broad complaint like "you always interrupt" without explaining the effect on the meeting. This template also helps people avoid overexplaining, apologizing for speaking up, or ending without a concrete next step. The rubric pushes the learner toward a calm, specific, and workable ask.

It works well as a short communication exercise in manager coaching, peer-feedback training, or meeting norms workshops. Start with a single attempt, then have the learner retry with a clearer request or firmer tone. You can pair it with a discussion of meeting etiquette, turn-taking, and how to handle interruptions without escalating. It also fits well alongside other assertiveness or feedback roleplays.

You can customize the meeting context, the relationship between the two colleagues, and how often the interruptions happen. If you want a gentler version, make Taylor less defensive; if you want a harder practice, make Taylor dismiss the concern at first. You can also adjust the learner objective to focus more on boundary-setting, teamwork, or future meeting behavior. The scenario should still stay specific enough that the learner knows exactly what happened and what they need to say.