Why You Understand English but Stay Silent in Meetings
Author: Ksenia Izotova
Last updated: September 2026
Last updated: September 2026
Why can you understand English but struggle to speak in meetings?
Understanding a meeting and entering it are different tasks. To speak, you have to choose a useful point, find an opening, formulate it while the discussion continues and manage the possibility of interruption or disagreement. Many people wait for a complete sentence and lose the moment. Others can speak in a lesson but stay quiet when status, speed or uncertainty raises the risk. Work on shorter contributions, predictable entry lines and the situations you actually face. Team behaviour matters too. Language practice cannot compensate for a meeting where nobody leaves space or where mistakes are punished.
This pattern does not prove that your English level is low. It shows that comprehension alone is not giving you reliable access to the conversation.
This pattern does not prove that your English level is low. It shows that comprehension alone is not giving you reliable access to the conversation.
This article addresses workplace communication practice, not a medical or psychological diagnosis. Persistent anxiety or distress may require support beyond language training.
Speaking asks you to do several things at once
During a meeting, you may be:
- listening to the current speaker;
- checking whether your point is still relevant;
- translating part of an idea;
- choosing how direct to sound;
- watching for a pause;
- worrying that someone will answer before you finish;
- deciding whether the issue is important enough to interrupt.
By the time the sentence is ready, the meeting has moved on.
The research concept of willingness to communicate helps explain why language knowledge does not automatically produce spontaneous speech. The original model describes willingness as situational and influenced by linguistic, communicative and social-psychological factors. Source: MacIntyre et al., “Conceptualizing Willingness to Communicate in a L2”
That does not mean every quiet employee has the same cause. It gives us a reason to look beyond vocabulary.
The research concept of willingness to communicate helps explain why language knowledge does not automatically produce spontaneous speech. The original model describes willingness as situational and influenced by linguistic, communicative and social-psychological factors. Source: MacIntyre et al., “Conceptualizing Willingness to Communicate in a L2”
That does not mean every quiet employee has the same cause. It gives us a reason to look beyond vocabulary.
Four meeting habits that keep you quiet
- Waiting for the full sentence
You prepare:
“I think the reason why we might perhaps need to reconsider the current implementation is…”
Someone else starts speaking.
Use the point first:
“I see a risk in the current implementation.”
Then explain:
“It retries the payment without checking whether the first request succeeded.”
A short first sentence gets you into the discussion.
“I think the reason why we might perhaps need to reconsider the current implementation is…”
Someone else starts speaking.
Use the point first:
“I see a risk in the current implementation.”
Then explain:
“It retries the payment without checking whether the first request succeeded.”
A short first sentence gets you into the discussion.
- Starting with an apology
“Sorry, my English is not very good, and maybe I misunderstood…”
The group is now thinking about your English before hearing the question.
Try:
“I may have missed one detail. Is the deadline for code complete or release to customers?”
The group is now thinking about your English before hearing the question.
Try:
“I may have missed one detail. Is the deadline for code complete or release to customers?”
- Agreeing because disagreement takes longer
“Yes, I agree.”
You may mean that you understand, that part of the proposal is reasonable, or that you do not want to slow the meeting.
Try:
“I agree with the goal. I’m not comfortable with the migration risk yet.”
The contrast is attached to a real decision.
You may mean that you understand, that part of the proposal is reasonable, or that you do not want to slow the meeting.
Try:
“I agree with the goal. I’m not comfortable with the migration risk yet.”
The contrast is attached to a real decision.
- Saving every point until the end
The facilitator asks for final questions. Your three earlier points now require a long explanation.
Raise the first relevant question when it changes the discussion:
“Before we estimate, can we confirm whether historical data is included?”
For more examples, see how to ask better clarifying questions in technical meetings.
Raise the first relevant question when it changes the discussion:
“Before we estimate, can we confirm whether historical data is included?”
For more examples, see how to ask better clarifying questions in technical meetings.
Prepare entry lines that have a job
An entry line should tell the group why you are speaking.
To clarify
“Can we pause on the scope?”
To add evidence
“I have one data point from Support.”
To disagree
“I see the delivery risk differently.”
To return to a missed point
“Before we close this, I want to return to the API limit.”
To ask for a decision
“Which option are we choosing today?”
These lines are short enough to retrieve under pressure. They also help listeners switch attention to your purpose.
To clarify
“Can we pause on the scope?”
To add evidence
“I have one data point from Support.”
To disagree
“I see the delivery risk differently.”
To return to a missed point
“Before we close this, I want to return to the API limit.”
To ask for a decision
“Which option are we choosing today?”
These lines are short enough to retrieve under pressure. They also help listeners switch attention to your purpose.
Make the contribution smaller
You do not need to deliver the entire analysis in one turn.
Long version:
“I wanted to say that we tested it yesterday with several different accounts and there were some problems, although I’m not sure whether the problem was related to permissions or maybe the feature flag…”
Shorter:
“We saw the failure on three test accounts yesterday. Permissions and the feature flag are still being checked.”
Then stop. Someone may ask the question that helps you continue.
Short contributions are useful for native and non-native speakers. They are easier to follow and easier to correct.
Long version:
“I wanted to say that we tested it yesterday with several different accounts and there were some problems, although I’m not sure whether the problem was related to permissions or maybe the feature flag…”
Shorter:
“We saw the failure on three test accounts yesterday. Permissions and the feature flag are still being checked.”
Then stop. Someone may ask the question that helps you continue.
Short contributions are useful for native and non-native speakers. They are easier to follow and easier to correct.
Use questions as a legitimate contribution
You do not need a finished solution to speak.
“What evidence do we have that the timeout is limited to Europe?”
“Who needs to approve the workaround?”
“What happens to requests that are already queued?”
“Are we discussing a target or a commitment?”
A precise question can reveal more senior thinking than a long summary. It shows that you are checking scope, evidence or consequence.
“What evidence do we have that the timeout is limited to Europe?”
“Who needs to approve the workaround?”
“What happens to requests that are already queued?”
“Are we discussing a target or a commitment?”
A precise question can reveal more senior thinking than a long summary. It shows that you are checking scope, evidence or consequence.
Recover after interruption
An interruption does not mean your English failed. The other person may be excited, rushed or used to a faster meeting style.
Come back with:
“I’ll finish the risk in one sentence.”
“There’s one condition I still need to add.”
“I think we are answering different questions. Mine is about existing customers.”
If the meeting moves on:
“I’ll put the point in chat and follow up with Nadia after the call.”
Then do it. This keeps the contribution connected to the work.
Come back with:
“I’ll finish the risk in one sentence.”
“There’s one condition I still need to add.”
“I think we are answering different questions. Mine is about existing customers.”
If the meeting moves on:
“I’ll put the point in chat and follow up with Nadia after the call.”
Then do it. This keeps the contribution connected to the work.
Change the environment as well as the language
If the same two people fill every pause, asking quieter colleagues to “be more confident” will have limited effect.
Useful meeting changes include:
Useful meeting changes include:
- sharing the decision question before the call;
- using a round when each function needs to report risk;
- pausing after a complex question;
- letting people add points in chat;
- naming whose input is needed;
- recording decisions and open questions;
- allowing a written follow-up before the decision becomes final.
A manager can say:
“I’ve heard from Backend. Before we decide, I want QA and Support to name any risk we have missed.”
This creates an opening with a purpose.
“I’ve heard from Backend. Before we decide, I want QA and Support to name any risk we have missed.”
This creates an opening with a purpose.
Practise in increasing levels of pressure
Do not wait to feel completely confident before moving stages. Repeat a stage until the action becomes familiar, then add one difficulty.
Review one meeting, not your whole personality
After the call, ask:
- Where did I have a useful point?
- What stopped me: language, timing, uncertainty, hierarchy or meeting behaviour?
- What was the shortest sentence that could have opened the point?
- Could I send a useful follow-up now?
- Which moment should I rehearse before the next meeting?
“I am bad at speaking” is too large to practise. “I need to challenge a date without sounding confrontational” is workable.
Frequently asked questions
Does staying silent mean my English level is too low?
No. Level may be one factor, but silence can also come from speed, lack of an opening, uncertainty about the topic, hierarchy or meeting culture. Test a specific speaking task before deciding what support you need.
Why can I speak in class but not at work?
A lesson usually gives you time, permission to speak and a clear topic. A work meeting adds consequences, interruptions, status and competing tasks. Practice should include those conditions gradually.
Should I translate my sentence before speaking?
For a complex or sensitive point, brief preparation can help. Translating every sentence during a live discussion is slow. Practise reusable structures that let you express the point directly in English.
What if colleagues speak too quickly?
Ask for the part you need: "Could you repeat the condition after the release date?" or "Can you put the three options in chat?" If speed prevents several people from contributing, the meeting process also needs attention.
Choose one visible action for the next meeting
Prepare one question or one 30-second contribution linked to the agenda. Say it early enough to affect the discussion. Afterwards, review that moment instead of judging the entire meeting.
UnifyHub’s one-to-one English lessons for IT professionals and role-specific corporate programmes use meetings, updates and difficult discussions from real work. Teams can book an assessment to identify where language, role expectations and meeting habits are limiting participation.
UnifyHub’s one-to-one English lessons for IT professionals and role-specific corporate programmes use meetings, updates and difficult discussions from real work. Teams can book an assessment to identify where language, role expectations and meeting habits are limiting participation.
Author: Ksenia Izotova
Last updated: September 2026
Last updated: September 2026