Back to Blog
Best Practice•2026-11-16•11 min read

When You Can't Follow Colleagues in Meetings

When You Can't Follow Colleagues in Meetings
TL
Team Laxis
Laxis Team @ Laxis

You're forty minutes into a call. Someone says a sentence, everyone else reacts, and you realise you caught maybe seven of the twelve words. You didn't get the number. You definitely didn't get the name. And a decision point is four seconds away.

Most people nod. Then they spend the rest of the meeting half-listening and half-reconstructing, so they miss the next thing too.

It happens in both directions — to someone working in their second language in an English-speaking meeting, and to someone in their first language on a call with a colleague whose sound pattern they haven't heard much of. Same experience, opposite chairs. Neither is a failure of intelligence or effort, and the fixes overlap.

It's a listening-conditions problem

Here's the reframe that makes everything else easier: comprehension isn't a property of you or of the speaker. It's a property of the conditions, and the conditions are usually terrible.

Count what's stacked against you on an average call. Audio compressed hard enough to strip out the detail that separates similar consonants. A laptop mic eighteen inches from someone's mouth in a hard-walled room. Crosstalk. Network jitter that eats a word. Jargon invented in a Slack thread you weren't in. Someone talking at 190 words a minute because they're late for their next call.

Now add a speech pattern you don't have much experience with. Not a defective one — an unfamiliar one. Your brain maps sound onto words using a model built from everything you've heard before, and if the input doesn't match it well, decoding slows. That's the mechanism.

Listening in a second language costs more effort. You're decoding sound, holding meaning, tracking the argument and often drafting your own contribution at once, all at someone else's speed. The exhaustion is a correct response to the workload, not evidence of a problem with you.

Worth knowing if you're the speaker: the fixes are mechanical on your side too. A headset mic, a pause at the end of each point, and numbers typed into chat do more for the people listening than slowing everything down. A test call in your meeting app lets you hear how you sound before the real one.

One more finding reorders the picture. Speech-perception researchers describe an interlanguage speech intelligibility benefit: for listeners who share a speaker's first language, and sometimes for other non-native listeners too, a proficient non-native speaker can be just as easy to understand as a native one (Bent and Bradlow, 2003). That undercuts the idea that some accents are simply harder: intelligibility is a relationship between two people, not a score on one of them.

What actually helps while the meeting is happening

Turn captions on. Always, not just when you're struggling. Reading and hearing the same sentence gives your brain two shots at each word, and it's the cheapest help there is. Leave them on permanently; our guide to the captions your meeting app already has shows where the switch lives.

Fix your own audio first. Headphones beat laptop speakers, mostly by removing room echo and letting you raise the volume without feedback. A surprising amount of "I can't follow this person" is actually "I'm listening in bad conditions on my end."

Ask early, and ask for the specific piece. Ten seconds after a sentence, a request for a repeat is trivial; four minutes later you have to explain you've been lost for four minutes. And "sorry, I didn't catch that" asks for everything again, where "I got everything up to the number — how many?" asks for one word and takes two seconds to answer. Precision reads as engagement.

Use chat. Names, figures, URLs, acronyms — typed once and the ambiguity is gone permanently. You can ask there without interrupting anyone, which is the lowest-friction option and criminally underused.

Write down what you did catch, not what you missed. When you lose a stretch, the instinct is to strain backwards. Don't. Note the fragment — "something about the Q3 forecast, check later" — and get back to the live conversation. Chasing one lost sentence is how it becomes five.

Make sure it's being recorded, with everyone's agreement. Knowing you can re-listen changes how you listen: you stop white-knuckling every sentence and start following the shape of the argument.

The phrases — steal these

Most of the awkwardness comes from not having a sentence ready, so people apologise — which frames the request as a confession. These are neutral, specific and fast.

Copy-paste phrases for when you missed something

When you missed a piece of a sentence

  • I got everything up to the date — what was the date?
  • One word got lost. Was it fifteen or fifty?
  • Can you spell that one? I want it right in my notes.

Naming what you need makes it a two-second answer.

When the pace is the problem

  • This part matters and I want it exactly right — can we take it slower?
  • Give me a second to write that down.
  • Hold on — I want step two before we get to step three.

Frame it around the density of the content, not anyone's delivery.

When you want it in writing

  • Could you drop that in chat? I'll copy it straight into the doc.
  • Would you mind typing the acronym? I'll look it up afterwards.
  • Can you paste the link rather than reading it out?

Nobody objects, and it helps two people who weren't going to ask.

When you want to check you understood correctly

  • Let me play that back: launch moves to the 14th, Dan owns the comms. Right?
  • So the blocker is the vendor contract, not the build. Right way round?
  • To make sure I've got this — option B, starting next sprint?

The safest one here: it surfaces a misunderstanding without anyone claiming they were lost.

When you've already asked once

  • Still not quite with you — can you give me the short version?
  • Let me try it back to you and you tell me where I'm wrong.
  • I think it's the audio on my end — could you type the key bit?
  • Let's take this offline — I'll message you straight after.

Two attempts is the ceiling in a group. After that, chat or a one-to-one is efficient, not a retreat.

When you're the one being asked to repeat

  • Sure — the number is 4,200, and I'll put it in chat.
  • Let me say that again more slowly, and stop me if it's still not landing.
  • Which part didn't come through? I'll take it from there.

Never apologise for how you speak, and never over-explain. Repeat it, put it in chat, move on. Treating the request as ordinary is what makes it ordinary.

Drop one word from all of it: "sorry." Compare "sorry, I didn't catch that" with "which date was that?" The second is shorter, clearer, and doesn't open with a claim of fault. Asking for information is a normal thing colleagues do about forty times a day.

The prep that makes the meeting easier

Everything above is damage control. The bigger wins are earlier, because comprehension is a prediction game: the more you know about what's coming, the less work each sentence takes.

Get the agenda ahead of time and read it properly. Knowing the middle twenty minutes is about the pricing migration primes your brain for that vocabulary, and ambiguous audio resolves far more easily when you half-expect the word.

Build your own glossary. Not the team's, yours — every acronym, codename and internal shorthand you've had to guess at. Quietly the highest-value twenty minutes you'll spend, because unexplained jargon is indistinguishable from a word you don't know, and it makes you feel like your language is the problem when it isn't.

Ask for the deck before the call. Reading slides while someone talks over them is hard for everyone and harder in a second language. Five minutes beforehand turns it into review.

Pre-listen to the person you find hardest to follow. If there's a recording of a previous meeting, play fifteen minutes with the transcript open; if all you have is the audio file, uploading it to Laxis (a free account works) makes one. You're training your ear on that voice, and the next live call will be noticeably easier.

Afterwards is where you actually catch up

Nobody follows 100% of a meeting, in any language. The difference between one that went badly and one that went fine is whether there's something to go back to.

A recording beats nothing, but scrubbing through 45 minutes of audio for one exchange is miserable. A searchable transcript is a different tool: type the keyword, land on the minute, read at your own speed. If you're on Zoom, getting Zoom transcription running properly takes five minutes.

If the meeting was in your second language, a version you can read in your first language closes the last gap — you get the exact wording and something your brain doesn't have to decode. That's the practical case for AI meeting assistants that translate live. Laxis, for instance, can put a translation under each line of the live transcript as people speak; it's a Premium feature covering 60+ languages, and you can set the spoken language yourself or let Laxis detect it. Afterwards the full transcript, summary and action items stay searchable. It's still machine translation: idiom, in-house shorthand and two people talking at once defeat it, so lean on it as a net, not the record of truth. And if you record a meeting, say so up front and get people's agreement wherever the law asks for it; our recording-consent explainer is general information, not legal advice. For setup, we've written up translating a meeting in real time separately.

Give yourself something to go back to. Laxis records the call, writes the transcript and summary, and on Premium translates each line live, so the two minutes you lost are a search away.

14-day Premium trial, no credit card. Try Laxis free

One habit to add: within an hour, send the two or three things you're not certain about as specific written questions. "Just confirming — is the vendor decision final?" costs one line and prevents the expensive version, which is acting on a decision you half-heard.

Quick fixes and structural fixes

Some take ten seconds. Some take a conversation, and pay back for years.

FixTypeEffortWhat it changesBest when
Turn captions onQuickOne clickA second channel per wordAlways. Leave them on.
Headphones, not laptop speakersQuickOne-timeRemoves room echo; raises volumeHard-surfaced rooms
Ask for the specific missing wordQuickOne sentenceRecovers a number, name or dateYou lost one detail, not the thread
Ask for it in chatQuickOne sentenceMakes spelling and figures exactProper nouns, acronyms, numbers
Play it back to confirmQuickTen secondsCatches misunderstandings earlyAny decision with your name on it
Search the transcript afterwardsQuickTwo minutesRecovers what you missedYou noticed a gap live
Build a personal glossaryStructuralAn hour, then ongoingRemoves the biggest false difficultyYou're new to the team
Get agendas sent a day aheadStructuralOne requestPrimes vocabulary; lets you prepareMeetings you attend weekly
Transcripts published by defaultStructuralOne setupMakes every meeting re-readableYour team records but nobody shares
Deliberate listening practiceStructural15 minutes, repeatedRetrains your ear on a voiceA colleague you often lose

Asking your team for changes without making it a thing

The instinct is to frame this as a personal difficulty, which makes it enormous to say and easy for a busy manager to defer. Ask for a mechanical change instead.

  • To your manager: "Two things would help me get more out of the Monday call — the agenda a day ahead, and captions on by default. I'll set the captions up."
  • To the group, in chat: "Turning captions on for everyone — shout if it's distracting."
  • To a meeting owner: "Could we circulate the deck the night before? I'd rather arrive with questions."
  • To the team, in a retro: "Can we make it normal to put numbers and names in chat?"

What about the colleague you personally find hardest to follow? Handle it as an audio-and-pace conversation, never an accent conversation, and go one-to-one. "I want to make sure I'm getting everything on our calls — would you mind dropping numbers in chat? Also, I think your mic is picking up a lot of room." That's a real request about real conditions, and it asks nobody to change how they speak. If the problem is your unfamiliarity rather than their audio, the fix is yours.

And if you run these meetings, much of it is fixable faster from the front of the room — here's how to run a multilingual meeting from the facilitator's chair.

The part that genuinely gets better

The most hopeful finding in the area: unfamiliar speech gets easier with exposure, quickly.

In one classic experiment, listeners processed Spanish- and Chinese-accented English more slowly than native speech at first, but the gap shrank within about a minute of listening, and sometimes after only two to four sentences (Clarke and Garrett, 2004).

So the colleague you find hard in week one is a solvable problem, and the solution is time rather than anyone changing. Speed it up: listen to recordings with the transcript open, so your brain gets the sound and the answer together.

Same in the other direction. If you're working in a second language, the fifth meeting is easier than the first and the fiftieth easier again — and people underestimate how much they've adapted, because the baseline moves with them.

Something to go back to. Laxis records and transcribes Zoom, Meet and Teams meetings, keeps them searchable for later, and on Premium translates them as they happen. 14-day Premium trial, no credit card. Download Laxis

Frequently asked questions

Why can't I understand my colleagues in meetings?

Almost always because of listening conditions rather than ability. Compressed call audio, cheap microphones, fast speech, overlapping voices, unexplained jargon and an unfamiliar sound pattern stack up, and any one can push a conversation past what you decode in real time.

How do I ask someone to repeat themselves without being rude or awkward?

Name the exact piece you missed instead of asking for the whole sentence again. Saying 'I got everything up to the date, what was the date?' is faster, easier to answer, and sounds like you were listening closely. Skip the apology, because it turns a request into a confession.

Is it rude to ask a colleague to slow down in a meeting?

No, and most people take it as a compliment about the density of what they're saying. Frame it around the content rather than the person: 'this part is important and I want it exactly right, can we slow down?' Asking the group is easier than asking one person.

Why is listening in a second language so exhausting?

Because you are doing several jobs at once: decoding sound, holding meaning, following the argument and often drafting your own reply, all at the speaker's pace rather than yours. That load builds across a day, so three back-to-back calls in a second language are genuinely more tiring than three in your first.

Do you get better at understanding an unfamiliar accent over time?

Yes, and faster than most people expect. In a classic 2004 study, listeners' processing of Spanish- and Chinese-accented English sped up within about a minute of exposure, sometimes after only two to four sentences. Listening to recordings of a colleague with the transcript open is a simple way to get more of that exposure.

What should I do if I missed something important in a meeting?

Go to the recording or transcript rather than reconstructing from memory. Search the keyword, read the surrounding two minutes at your own pace, and if it's still unclear send one specific written question. Guessing at a decision you only half-heard is how expensive misunderstandings start.

Should I tell my manager I'm struggling to follow meetings?

Yes, but ask for a mechanical change rather than describing a difficulty. Asking 'could we get the agenda a day ahead and turn captions on by default?' is a process request your manager can act on immediately, and it helps people who never said they were struggling.

Nobody catches everything

The room is not as sharp as it looks from where you're sitting. Native speakers mishear numbers constantly. People nod along to acronyms they've never decoded and look them up afterwards. In lingua franca research there's a documented habit called "let it pass" — quietly allowing an unclear stretch to go by in the hope it clears up from context. Alan Firth described it in 1996, and it is common. The person across from you who looks perfectly comfortable is doing a version of what you're doing.

The difference is who has a system for catching what got past them. Captions on. A specific question instead of an apology. A transcript to go back to. That's it, and it takes about a week to build.

Related Product

Laxis Meeting Assistant

Automate your notes today.

  • Bot-free notes for Zoom, Google Meet, Teams and in-person meetings
  • AI summaries, action items and follow-ups in 60+ languages
  • Mac, Windows, iPhone and Android, with a free plan

Start for free, no credit card required.

Learn More ▷