Speaking Up in English Meetings: Interrupting, Holding the Floor, and Disagreeing Without a Fight

Introduction: the problem is not your vocabulary

Think of a day when you sat through an English meeting without saying a word. Afterwards, the sentence you wanted to say arrives fully formed. The grammar is right. The words are right. It just did not come out while the meeting was running.

This is not a vocabulary problem. It is a problem of never finding the place to speak.

People used to Korean-language meetings usually wait like this: someone finishes, there is a short quiet, and you go in there. In an English meeting that quiet almost never comes. When it does, it lasts half a second. Waiting is a strategy that fails structurally.

What English meetings have instead is a fixed set of signals that announce you are taking the floor. These signals are closer to idioms, and there are fewer than ten of them. Native speakers use exactly the same ones. Which means this is not a talent — it is a list.

This article is about that list. Before laying the phrases out, I want to explain why each one sits where it does. Once you know the structure, forgetting one phrase does not matter because you can swap in another.

English meetings do not wait for silence

Conversation analysis has established one thing very clearly. Gaps between speakers in English conversation are extremely short, and they often overlap. Starting before the previous person has fully finished is not rudeness, it is normal.

Korean meetings do not have long gaps either, but the way the next speaker is decided is different. Seniority and seating order often set the sequence, so waiting for your turn feels natural. In English-language meetings, and especially at American tech companies, there is no sequence. Whoever starts talking takes the slot.

There is one thing not to misread here. This does not mean "you have to be rude." If anything, the opposite. English meetings have a whole apparatus developed specifically to make interrupting polite. Use the apparatus and interrupting is not rude; skip it and just start talking, and it is.

So what you need to learn is not courage. It is the apparatus.

One honest caveat: this temperature varies a lot by company and country. Dutch and Israeli teams are far more direct, and overlapping speech is the baseline. Japanese organisations and formal British settings run much closer to a queue. Treat the phrases below as roughly the median of Anglo-American corporate settings, then watch your actual team for a few days and adjust.

A contribution has four steps

Cut up what a good speaker says in an English meeting and you almost always get the same four pieces.

Step 1, send a signal. You announce that you are coming in. One short line, like Can I jump in here?

Step 2, label what is coming. You say first whether this is a question, a concern, a suggestion, or just one piece of information. Something like Quick question — or One concern —.

Step 3, say the thing. This is the substance, and two or three sentences usually cover it.

Step 4, hand the turn back. You finish and return the floor. That's all from me. Or you throw a question to someone.

Put the four together and it looks like this.

Can I jump in here?                       ← step 1: signal
Quick question on the timeline —          ← step 2: label
are we counting the QA week in that four? ← step 3: content
                                          ← step 4: the question hands it back

The most underrated of these is step 2. Most Korean learners use only steps 1 and 3. But the piece that actually secures the floor for you is step 2.

Here is why. While you are talking, people are continuously deciding "is this what we need right now?" Without a label, you do not really hold the slot until that decision resolves. Say One concern — up front, and the listener immediately finishes the filing — "ah, a concern" — and waits for the content. A contribution that has already been classified does not get cut off.

Step 1: the signal that you are coming in

Can I jump in? is the safest. It works in internal meetings, client meetings and video calls, and it works regardless of seniority. If you memorise one, memorise this.

Quick thought is short and low-cost, which is why in practice it is the one people use most. It is casual, though, so in a formal first meeting with a client, Can I add something? is the safer choice.

There is one to watch out for. Can I get a word in? literally means "may I say one thing," but in practice it carries the complaint that you have been trying and getting blocked repeatedly. Do not use it unless that is what you mean. Conversely, if that really is the situation, it is exactly the right phrase.

Step 2: the one-word label

Just a data point is especially useful. It declares that you are placing a fact without arguing for a conclusion, so the risk of being contradicted is close to zero and you still contribute. When English is not yet comfortable, this is the cheapest way to have a presence.

Not to derail, but is good because it is honest. Admit the detour yourself and people become more generous about it, not less.

One to be careful with is Devil's advocate for a second —. It means "let me deliberately argue the other side," it is common at American companies, but a fair number of people have gone off it lately. It was too often used as a device for voicing your own opinion while dodging responsibility for it. If you really need it, saying I'm not sure I agree, and here's why as your own position earns more trust.

Step 3: not getting cut off

You have probably had the experience of starting, then getting cut off in your second sentence. There are dedicated phrases for exactly this.

The first one is the heart of this table. Declare the count and the slot is booked in advance. Say Two things. and give the first, and the whole room knows you still have the right to the second, whoever comes in. If you do get cut off, Sorry, that was one of two brings you straight back.

Bear with me means "stay with me for a moment," and it is worth laying down before a long explanation. Note that writing it as Bare with me is a famous typo that means something entirely different, so watch it in writing.

Sorry, I wasn't quite done is strong, but sometimes you need it. What matters here is not the words but the delivery. Said flatly and administratively, with no anger in it, it causes no problem at all.

Going back to a point the room skipped

This is the most common loss in English meetings. You had a good question, and while you were assembling the sentence the topic moved on. Winding it back, though, is completely permitted, and there are dedicated phrases for it.

Can we park that? came out of British and Australian corporate settings and is now used widely. It means "let us not handle this now, but put it on the list." Because it signals deferral rather than abandonment, it meets very little resistance.

We skipped past X — is that decided? has a good shape. It states a fact without blame, and it ends in a question, so someone has to answer. For reviving a decision that got walked past, there is no better sentence.

circle back, very common at American companies, means the same thing. That word is a poster child for corporate jargon and gets mocked for it, so if you want to be safe, use come back to. The meaning is identical.

Partial agreement: when you do not agree with all of it

The position you most often need in a meeting is in fact neither a hundred percent for nor against.

These share one structure. Name the part you agree with, specifically, first; then keep the disagreement narrow. Just saying I partly agree leaves the other person unable to tell which part, so they go on the defensive.

I don't disagree, but is an interesting one. Literally it says "I am not against this," but the real nuance is closer to not actively in favour. It is the polite thing to say when you are not happy, so if you hear it, read it as the other person not being fully convinced.

Disagreeing without confrontation

The top one, What's the thinking behind that?, is the most useful of all in practice. Because it asks for the reasoning rather than rebutting, the other person does not go defensive, and while you listen to the answer the problem often exposes itself. A big advantage is that you can use it even when you are not ready to disagree yet.

Can I push back on that? is extremely common at American tech companies and has settled in as the standard way to announce disagreement. Because it is announced, even sharp content does not read as a personal attack.

Here is a point Korean learners often get wrong. Disagreement itself is not rude in English. What is rude is disagreeing without a reason. English-language meetings carry a strong expectation that disagreement comes with grounds, so a bare I disagree reads as mere negation. Attach the grounds and even fairly hard disagreement is received as a normal contribution.

That said, the cultural spread here is large too. The same sentence is unremarkable in a startup engineering meeting and heavy in a formal executive session or in front of a client. What sets the strength is the room more than the phrase.

One phrase needs care: Help me understand why we're doing X. It looks humble, but it is frequently used by senior people interrogating junior ones, so depending on context it can land as quite intimidating. If you genuinely want to understand, Can you walk me through the reasoning? is far safer.

When you did not catch it: asking again without losing face

This may be the most practically important section here. Miss one thing in a meeting and the next five minutes are gone, and with them your chance to speak.

There is one core principle. Do not ask for the whole thing again — point at the piece you missed.

The third one is the heart of this table. Put Just to make sure I've got it — in front and attach a summary of what you understood, and formally this is a confirmation request, not a confession of failure. You can use it having caught only half; if you are wrong the other person corrects you, and if you are right the whole meeting gets tidied up. Either way you lose nothing.

Acronyms especially. Every company has dozens of its own, and it is not only new hires who do not know them — people three years in do not either. Ask, and usually two or three other people quietly relax.

Pardon? works in British English but can sound slightly formal or old-fashioned to Americans. Sorry, what was that? travels better. Come again? is casual American, and Huh? is too relaxed for a meeting.

When you get called on with no warning

There are moments when your name comes up and you are not ready. What you need here is time and honesty.

The last one matters most. Saying you do not know, plus by when you will find out, always beats a plausible-sounding guess. A guess passes fine in the room and comes back twice as large next week. Simply adding the deadline turns "I do not know" from incompetence into management.

The Short answer is X, longer answer is Y shape is very useful too. It lets you give an immediate answer while holding back on precision.

Remote meetings run on slightly different rules

On video, the strategies above do not transfer cleanly. Latency is the reason. By the time the signal that someone has finished reaches your ear it is already late, and several people open their mouths at once.

So remote runs on explicit tools rather than implicit signals.

The ritual for talking over each other is fixed. Both stop, one says Sorry, go ahead, and the other talks. Endless mutual yielding wastes time, so when a second yield comes back to you, just speak.

The most underrated remote tool is the chat. If you cannot find the gap, write one line in the chat. A good facilitator reads it and opens the floor for you: Youngju has a question in the chat. This is not avoidance — it is a legitimate way to participate in a remote meeting.

Things better left undone

Opening with With all due respect. Literally it means "with full respect," but it has hardened into a signal that something rude is coming immediately after. It is especially well known as ironic in British English. If you actually want to be respectful, I see it differently is far more respectful.

Prefacing everything with an apology for your English. Attach Sorry, my English is not good every time and two things happen. The weight of what you say is discounted in advance, and your listener carries the burden of reassuring you each time. Saying it once on a new team is fine, but do not make it a standing prefix. What you need is not a pre-emptive apology but the right repair sentence in the moment.

Stacking hedges. I think maybe we could possibly perhaps look at... One softener in English is politeness; three on top of each other read as no confidence. Use one.

As I said before. The literal meaning is neutral, but it lands with audible irritation — "I already told you." When you have to repeat yourself, To restate that — or simply saying it again works better.

Saying I have a question and then going silent. You declare, and while you assemble the sentence the slot is taken. Say the label and the content together.

Attaching Good point to every colleague's contribution. Evaluation is fundamentally a top-down act, so it can sound like you are scoring people each time. The effect is weak and on many teams nobody minds at all, but there is no reason to make it a habit. If you agree, Agreed — and that also affects X is stronger than That's a good point, because it adds content.

Waiting for complete silence. The first and last principle of this article. That silence is not coming.

A worked example: sprint planning

PM:  So the plan is to ship the payments migration by the 30th.

Me:  Can I jump in here?
PM:  Sure.
Me:  Quick question on the timeline —
Me:  does the 30th include the QA week, or is that on top?
PM:  It includes it.

Me:  Okay. Two things then.
Me:  First, that gives us about six working days for the backfill.
PM:  Right.
Me:  Second — and this is the concern —
Me:  we found bad timestamps in about forty thousand rows last week.
PM:  How bad?
Me:  I don't have the exact number in front of me.
Me:  I'll get it to you by end of day.

(someone else moves the meeting to a different topic)

Me:  Before we move on, can we close out the backfill question?
PM:  Go ahead.
Me:  I'd want to see the row count before committing to the 30th.
Me:  What's the thinking behind that date? Is it tied to something external?
PM:  It's the board demo.
Me:  That's useful to know. Then I'd suggest we ship the read path by the 30th
Me:  and the backfill the week after. Would that work for the demo?
PM:  Let me check. Good — put that in writing?
Me:  Will do. That's all from me.

Here is what actually happened in that exchange. You came in with a signal, secured the slot with a label, booked a second turn by declaring the count, said you did not know and attached a deadline, wound the topic back when it moved on, and asked for reasoning instead of rebutting. Every sentence is short. There is not a difficult word in it.

Try this today

Use only these four in your next meeting.

1. One entry signal: Can I jump in here?
2. One label: Quick question — or One concern —
3. One slot reservation: Two things.
4. One check-back: Just to make sure I've got it — you're saying ...?

All four are about five words long. What a meeting requires is not fluency but an entry point. One short signal travels much further than one perfect paragraph.

Read next

• Asking and saying no in office English — the next article. What to request and what to refuse with the floor you just took.
• Getting better at English without the situations — how to design the practice that turns the phrases above into reflexes.
• Conversation practice — trains the receiving side of a conversation: interrupting and checking back.
• Shadowing practice tool — short signal sentences have to be memorised as sound to arrive mid-meeting.