How to Respond When You Interrupt a Colleague

What should you do the moment you notice the interruption?

Stop speaking, acknowledge the cut-in briefly, and give the colleague the floor: “I cut in. Please finish.” Then listen through the rest of their thought before explaining what you wanted to add. The repair works by changing what happens next; it does not require you to decide in that instant whether your feeling of being unheard was accurate.

Illustration: a colleague is explaining a concern and you begin answering before they have finished. You catch yourself, say, “I interrupted you—go ahead,” and wait. After they finish, you can still raise your concern or ask a clarifying question. The order matters: finishing the explanation first lets you respond to the point they actually made, rather than to the part you anticipated.

Keep the acknowledgment short. A long account of why you spoke over them can consume the turn again and make the repair about your intention. If one detail is essential to understand what they mean, ask for that clarification; otherwise, hold the question until they finish. You are not withdrawing your view or promising agreement. You are restoring enough space for both people to put their thoughts into the conversation. Once the colleague has finished, take a beat to check what you heard before moving to your point. That small gap helps keep the exchange from snapping straight back into competing turns.

What makes the urge to jump in harder to resist?

When you feel unheard, an unfinished thought can seem as if it will vanish unless you say it now. The concern may also feel time-sensitive because it matters to the work. That urgency explains the impulse; it does not tell you whether the colleague has understood, nor whether an interruption will make your point easier to hear. A modest pause gives the other person room to complete the information you may need before you answer.

The urge can also come from trying to protect the substance of the discussion: you may be anticipating an objection, a missed constraint, or a decision that will be hard to revisit. But speaking sooner does not guarantee that the point will land. While you formulate the next sentence, you can miss the rest of the colleague’s explanation, including information that changes what you want to say. Letting them finish is a way to avoid answering an incomplete version of the conversation.

There is a narrow piece of experimental evidence for protecting attention during a conversation. In “Effects of an early interruption and note taking on listening accuracy and decision making in the interview,” participants watched a recorded employment interview with a staged interruption and completed a test of how accurately they recalled its content. The interruption and note-taking conditions affected listening-accuracy scores; the highest reported accuracy, 79%, occurred when note-taking was required and there was no interruption. The manipulations did not significantly change participants’ overall suitability judgments. This was a scripted interview viewed by professional interviewers and managers, not a live exchange in which the speaker interrupts a colleague. It measured recall and judgment, not whether a repair phrase returns trust or resolves the speaker’s concern. It therefore supports only a limited practical inference: preserving a thought while allowing speech to continue can be worth trying when accurate listening matters.

The Open University’s “Effective communication in the workplace: Tactics to avoid interrupting” offers one simple way to manage that competing demand: jot down a few words about the point you want to make, allow a short silence, and speak when the other person has finished. The course presents this as instructional advice, not as a tactic tested in a controlled trial. Keep the note small—perhaps a key term or question—so it reminds you what to return to without becoming a speech you rehearse while the colleague is talking. A quiet pause may be enough; writing is optional.

Use the step only when it helps. If you notice yourself preparing a rebuttal, put the thought aside long enough to hear the next sentence. If you fear losing a specific work point, record a few words and return your attention to the speaker. The interview experiment cannot establish that this will change a colleague’s response, and the Open University lesson does not report a measured outcome. Together they offer a restrained reason to try a low-cost pause: it leaves the conversation intact while you keep track of what you still need to say.

Sources: Effects of an early interruption and note taking on listening accuracy and decision making in the interview; Effective communication in the workplace: Tactics to avoid interrupting

Does disagreement mean your colleague did not hear you?

No. A colleague can understand the concern and still judge the options differently. Agreement tells you that the other person reached the same conclusion; it does not, by itself, show whether they listened carefully. The reverse is also true: disagreement can feel like evidence that your point never registered, even when the person can describe it accurately. So when the urge to interrupt returns after a colleague says no, treat that feeling as a reason to check what they understood, not as proof that they failed to hear you.

The finding is documented in “Disagreement Gets Mistaken for Bad Listening.” Across 11 studies involving 3,396 adults, researchers varied whether a listener agreed while holding listening behavior constant or controlling for other positive impressions. Speakers repeatedly rated the disagreeing listener as worse at listening. The authors also report that speakers’ confidence in their own view helped explain this inference: if I believe my conclusion is right, another conclusion can register as a failure to recognize what I said. This is evidence about how speakers judge listening in study conversations. It does not establish that disagreement is always misunderstood, or that the colleague’s reasoning is sound.

This distinction changes what counts as a useful next move. If you are waiting for a nod or a yes before you believe the colleague has taken you seriously, you may keep pressing for agreement when the remaining issue is the decision itself. A more informative response is whether they can name the consequence you raised and give a reason for their choice. For instance, “I understand that you’re worried the handoff could leave the client without an owner; I still think we should proceed because the receiving team has confirmed coverage” shows comprehension alongside a different judgment. That response might still leave you dissatisfied, and the reasoning may deserve scrutiny. But it gives you something specific to discuss: the coverage assumption, who verified it, or what would change the decision. A bare refusal gives less information, so it is reasonable to ask what consideration the colleague is using.

Illustration: after your colleague finishes explaining why they prefer a different project option, ask, “Could you summarize the concern I raised, so I can check whether I explained it clearly?” If they can identify the concern and explain why they weigh the trade-off differently, understanding and agreement have come apart. You can then address the reasoning, add a missing fact, or accept that the decision remains different. The point of the question is to test whether your concern made it into their account—not to make them repeat your words until they change their answer.

A good summary is useful evidence that the concern was understood, but it cannot tell you whether the practical risk has been answered. If the colleague names the wrong issue, correct that specific misunderstanding. If they name it accurately and still disagree, ask what consideration drives the decision. And if the same interruptions or unanswered concern recur, pay attention to that pattern directly; one disagreement study cannot settle what is happening in a particular working relationship.

Sources: Disagreement Gets Mistaken for Bad Listening

How can you check understanding and still keep your point?

Ask for the colleague’s version of your concern, correct one important mismatch if there is one, and then state your point in a single sentence. For example: “What did you hear as my main concern?” If the answer misses the central issue, try: “The part I want to make sure is clear is the risk to the handoff.” Then give your position plainly: “I think we should confirm ownership before we commit to the date.” This is a conversational pattern you can adapt, not a validated script. It gives you a way to find out whether your meaning arrived while preserving your right to make the case.

Keep the sequence brief enough that it does not become a second speech. Ask one open question, listen to the answer, and decide whether it changes what you need to say. If the summary is close but misses a qualifier, correct that qualifier rather than starting the whole explanation again. If the colleague has understood the point, move to the reason for the disagreement or the decision still needed. You might say, “Yes, that’s the concern. My recommendation is to pause until we know who owns the handoff.” The aim is not to win a test of listening; it is to put the concern and your request in a form the other person can answer. If the account is already accurate, there is no need to demand another paraphrase.

The check works only if you leave room for an answer you did not expect. A colleague may summarize your concern accurately and then explain why they assign it less weight, have other information, or recommend a different response. In that case, the understanding check has done its narrow job: it has helped distinguish a communication gap from a difference in judgment. You can ask about the reasoning or supply a missing detail. Repeating the concern more forcefully may not add information, and a paraphrase should not become a demand for agreement disguised as a question.

“Effects of Empathic Paraphrasing: Extrinsic Emotion Regulation in Social Conflict” offers limited context for why a concise check may be worth trying. In the experiment, 20 German-speaking adults discussed a current or recent nonviolent conflict in a structured interview. After participants described an aspect of the conflict, the interviewer either paraphrased their account or took notes. Participants reported a shift toward less negative emotional valence following paraphrasing. Some voice measures also changed, while physiological indicators did not show simple calming: heart rate and skin-conductance response were higher in the paraphrase condition. The result concerns short-term responses in this small social-conflict interview, not a workplace interruption or a universal conversational formula.

There is another reason to keep the claim modest: the paraphrase condition involved the interviewer speaking, while the note-taking control did not provide equivalent speech. The authors note this as a limitation, and some recorded measures had fewer observations because of technical data loss. The experiment therefore cannot show that the paraphrase alone caused the reported shift, much less that a colleague will feel calmer or change a decision. Use your wording to check accuracy, then invite correction: “Have I got that right?” If the summary flattens the risk or leaves out a condition, revise it before making your point.

Sources: Effects of Empathic Paraphrasing: Extrinsic Emotion Regulation in Social Conflict

When does a work concern need an answer after the conversation?

A restored speaking turn answers one question: did your colleague get to finish? It does not necessarily answer the work question that prompted you to speak. If the conversation ends with acknowledgment but leaves a decision, risk, or responsibility unresolved, ask what response is still needed. Sometimes an accurate summary is enough; sometimes you need a decision, a fact checked, or a named person to return with information. The distinction is practical: feeling heard in the exchange and getting the work issue resolved can be separate outcomes.

The qualitative study “Feeling Heard: Experiences of Listening (or Not) at Work” helps explain why. Researchers interviewed 41 employees at one bank and analyzed 81 retrospective stories about workplace listening. In some accounts, conversational behavior—such as attentive responses—did not settle whether the speaker felt heard. What the speaker needed and expected mattered too. Some stories turned on later action or reasonable follow-up; an initially attentive conversation could feel incomplete when expected action never came. The study describes employees’ accounts, not an objective rating of who listened well, but it identifies a useful question to ask after a difficult exchange: what outcome would make this concern feel addressed?

That question should be specific enough to distinguish acknowledgment from the next step. If you only need your colleague to understand your position, checking that they can describe it may close the loop. If a decision is pending, ask when it will be made or what information is missing. If the person cannot decide, ask who can give an answer. A follow-up request is not a demand for your preferred result. It is a way to make the remaining work visible, so neither person has to guess whether the topic is finished or merely paused.

Illustration: imagine a discussion about whether a proposed schedule can meet a required review date. You have explained the concern, and your colleague has acknowledged it, but nobody has checked the reviewer's availability. You might say, “The open question is whether the reviewer can return comments by Thursday. Could you check with them and tell me what timing is possible? If you are not the right person to ask, who should own that check, and when can we reconnect?” The request names the unresolved question, the response needed, and a route back to it. If Thursday is not possible, a reasoned answer that explains the constraint and offers a realistic alternative still answers the request; it need not produce the outcome you hoped for.

Agreeing on an owner and a return time makes a pause legible. “I’ll check and come back tomorrow afternoon” gives both people a reference point. If the other person lacks authority, the useful next step may be identifying the decision-maker together rather than treating their inability to approve the request as indifference. You can also ask what they can confirm now and what requires another person. This keeps responsibility attached to the work question without assigning responsibility for the entire problem to the person who happened to hear it.

Keep the scope proportionate. A minor preference may need only acknowledgment; pressing for a formal decision or deadline could add needless weight. A material dependency, commitment, or risk may remain consequential even after the conversation felt respectful. In that case, clarity about who will respond and when helps you plan. The request can leave the substance open: your colleague may explain why the proposed option cannot proceed, or why the concern will be handled another way. What matters is that the response addresses the actual question, rather than leaving you to infer a decision from silence.

The “Feeling Heard” interviews were retrospective and came from one bank, so they do not show that every speaker expects action or that every expectation is reasonable. Nor can one colleague always provide the answer. Use the finding as a prompt to clarify your need, not as proof that acknowledgment is inadequate. If a response is needed, ask what the person can answer, who has the relevant authority, and when a return is feasible. A clear refusal with a rationale can resolve the request; an unanswered question may need an owner or an appropriate work channel.

Sources: Feeling Heard: Experiences of Listening (or Not) at Work

What changes when the interruption becomes a recurring meeting pattern?

A single exchange calls for a response to that exchange. A recurring meeting problem may need a change in how the group handles turns or records open questions. Look for a pattern you can describe without guessing at anyone’s motive: for example, several people begin speaking before others finish, concerns repeatedly arrive after a decision, or questions are discussed but leave the meeting without an owner. If the same obstacle shows up across meetings, another private repair may not address the process that keeps reproducing it.

“Learning to listen: Downstream effects of listening training on employees' relatedness, burnout, and turnover intentions” examined structured group practice over a longer period. Its first quasi-field study included 51 high-tech employees and compared work teams taking a 12-hour listening course with a waiting-list control. The second included 73 customer-service employees in two insurance branches and compared a 15-hour course with work-related lectures. The authors reported higher colleague relatedness and lower burnout after training in both studies; turnover intention was also measured and reported lower in the second. Measures were taken after the courses and again three weeks later. These findings concern substantial training, not a brief intervention during a meeting.

The studies make it reasonable to take listening as a group practice seriously when the difficulty recurs. They do not identify a winning meeting rule or show that a particular agenda, facilitator, or note-taking procedure will reproduce the reported outcomes. The conditions were assigned by intact work teams or branches, with few organizations and limited condition-level replication; local features could have contributed. Keep the inference modest: a repeated problem may justify trying a visible procedural adjustment, then checking whether the specific obstacle changes.

Start from what is happening in the room. If some participants rarely get a turn, a facilitator could track speaking turns and invite contributions before closing the topic. If concerns arrive only after the group has settled on an option, a shared agenda could reserve space for concerns before the decision. If people leave unsure what happened to a question, the group could record an owner and a return date. These are practical suggestions, not tactics tested by the training studies. Choose the smallest adjustment that matches the observed difficulty instead of introducing several rules at once.

Make the request concrete and non-accusatory: “I’ve noticed that we often finish this agenda item before everyone has raised a concern. Could we pause for questions before deciding on the next item?” Or, where follow-through is what disappears: “Can we note who will check this point and when we’ll revisit it?” The first describes a turn-taking issue; the second makes an open task visible. Neither requires deciding that one person is deliberately shutting others out. A procedure can give the group a shared cue and make it easier to notice whether the same people are still being missed.

After trying one change, review the same observable feature that led you to ask for it. Are concerns being raised before the decision? Does each unresolved question leave with a named owner and a date? Are turns more evenly available, or is the difficulty still present? This is a practical check, not a claim that the group has measured listening quality. If the adjustment changes the process but not the underlying problem, the group may need a different response, clearer decision authority, or a conversation about the work conditions producing the pattern.

Because the quasi-field studies involved intensive courses in a small number of organizations, they cannot tell you which process option will work for this particular group. Treat the course findings as evidence that group listening has been studied over weeks, not as proof for any one meeting tactic. If the recurring issue concerns an unanswered safety concern or material work risk, use the appropriate reporting or escalation channel as well; conversational etiquette cannot substitute for a needed operational decision.

Sources: Learning to listen: Downstream effects of listening training on employees' relatedness, burnout, and turnover intentions

What can you learn from reviewing your own response afterward?

Review one exchange by reconstructing what you did, not by deciding what kind of person you are. Start with the moment you noticed the urge to interrupt: what had the colleague just said, and what did you want to make sure they understood? Then look at the next observable action. Did you pause long enough for them to finish? If you cut in, did you return the floor? After hearing the rest, did you make a clear request, or did the conversation end with the concern still unstated? These details give you something specific to notice next time. You are recording what happened in this particular conversation, so the next observation can test a specific action rather than confirm a label you gave yourself.

Keep the account narrow. “I interrupted after hearing that the review date might move; I apologized, let my colleague finish, and asked what information would settle the date” describes an exchange. “I am a bad listener” turns it into a verdict about yourself. “They do not respect me” turns your interpretation into a claim about your colleague’s motive. Neither conclusion follows from the interruption alone. The review is useful when it separates the event, your response, and what remains uncertain about the other person’s intent.

Choose one behavior for the next conversation. You might notice whether you wait until a colleague finishes before answering, whether you say what you need in one sentence, or whether you ask who will follow up and when if a work question remains open. Pick the behavior that fits the moment you reviewed. A small target makes it easier to recognize whether you tried it; it does not require you to judge the whole conversation as a success or failure. If the concern was resolved by the explanation, there may be nothing more to request.

One exchange is a small sample shaped by its timing, stakes, and participants. It can help you spot a response worth practicing, but it cannot establish a stable trait or explain why a colleague spoke as they did. The same person may respond differently when a deadline is near, when responsibilities are unclear, or when they have information you have not heard. Keep those possibilities open while still taking responsibility for the action you can observe: whether you interrupted, whether you returned the floor, and whether you made the remaining request answerable.

If a more structured prompt would help, the private Emotional Skills Profile at /assessment has 32 items and provides recent-behavior summaries alongside judgments on authored scenarios. Those are two kinds of reflection: what you report doing in recent situations and how you respond to described emotional situations. The profile is an educational reflection aid, not a standardized ability verdict; it has no validated norms or established ability-test validity, and it cannot guarantee a change in how a conversation goes. You can review one exchange without taking it. If you do use the profile, treat its prompts as a way to notice a behavior to practice, then return to the next real conversation and observe that behavior there.

Sources: Emotional Skills Profile

Make the next request concrete

If something remains open, try: “I hear your view, and I may still disagree; could you tell me [the answer or decision I need], or who will follow up by [time]?” Name the unresolved work question and a realistic return point, leaving your colleague free to explain or disagree. Make the request fit what is actually missing. If you need a decision, ask for the decision and when it can be made; if a fact needs checking, ask who can verify it and when they can report back. Avoid hiding several requests inside one question. A colleague may have a different answer, may need more time, or may point you to someone with the authority to decide. Their response gives you a next step: continue the discussion with the relevant information, agree on a return time, or use the appropriate work route if a material risk remains. If the explanation has resolved the concern, stop there; no extra procedure is needed. A clear request lets the other person answer the work question without requiring them to endorse your preferred option.

Questions readers ask