Watch any MBA team in week three. Someone spots a real problem with the model. Four other people are already half a beat into talking about something else. The person with the correction starts a sentence twice, gets cut off twice, and stops. The error ships in the deck and comes back in the professor's feedback ten days later.
The team will describe this later as "she didn't say much in meetings." What happened is that a half-second of extra processing—the ordinary cost of working in your second or third language—lost every race for the floor in a room where it goes to whoever talks first. That's an airtime problem, not a competence problem. Teams misdiagnose it constantly, reading fluency as intelligence and quietness as disengagement. Both are wrong, both are expensive, and the fix is structural. Change the meeting, not the person.
Why the fast meeting loses your best analysis
Free-for-all meetings distribute airtime by reaction speed. Not by insight, not by who did the reading—by who gets the first syllable of an interruption out fastest.
Working in a second language means doing two jobs at once: following what's said, and assembling what you want to say in a grammar you're constructing rather than retrieving. The extra half-second isn't hesitation or uncertainty about the content. But where the gap between speakers is a quarter-second, it loses every time.
If four people speak freely and one speaks only in the two or three gaps that open per hour, the team has decided to run on 80% of its analysis. Teams routinely find in a retrospective that the quietest person had caught the error nobody acted on.
Fix the meeting, not anyone's speaking speed
Four changes, none of which requires anybody to be more assertive.
Circulate the agenda before the meeting. The day before, written as the actual questions you'll decide. "Do we scope to the US only?" is preparable; "market sizing discussion" is not. Now anyone can arrive with the point composed instead of composing it live while listening. Highest-return change on the list.
Run one round-robin pass. Everyone speaks once on each substantive question before anyone speaks twice. Stilted for two meetings, then normal. It removes the need to win an interruption to be heard—the mechanism actually doing the damage.
Give written input equal weight. A channel where people post analysis before or after the meeting, and the team acts on it. The participation ranking usually inverts outright: whoever said least in the room writes the most rigorous three paragraphs on the thread. That's what the analysis looked like all along, without a stopwatch attached. Defining what each channel is for keeps it from becoming where things go to be ignored.
Slow the meeting by about a second. One deliberate beat after someone finishes before the next person starts. It costs four minutes an hour and changes who gets to talk. Agree on all four at kickoff, while norms are soft.
Habits native speakers can drop at zero cost
These carry no meaning and a lot of comprehension load.
- Idioms and sports metaphors. "Circle back," "move the needle," "red zone," "take it offline." Each has a plain version that's shorter and clearer. Football and baseball metaphors are the worst offenders because nobody hears them as jargon.
- Humor built on cultural reference. A joke about a TV show is fine. Building the team's shorthand on it is how someone ends up nodding along to half of every meeting.
- Acronyms, including the ones you think are universal. Expand the school ones, the industry ones, and the ones from your old job. Two seconds.
- Softening a directive until the instruction disappears. The big one, and a specifically American habit. "It might be worth maybe taking another look at the assumptions" is an instruction: fix the assumptions. Every hedge is politeness convention, and politeness convention doesn't survive translation. What arrives is a mild suggestion, cheerfully filed and not acted on—and you're annoyed a week later about something you never asked for. Say the thing; be warm separately.
Blunt in English is often the right register
The reverse direction costs just as much. "This number is wrong" is neutral and entirely polite in plenty of languages. Rendered into English by someone who learned it as a language of precision rather than cushioning, it lands as an attack on an ear expecting three layers of hedging first.
It almost never is one. It's a register mismatch, and the speaker usually knows they came out harder than they meant—its own quiet tax. Assume the professional reading. If the team wants a softer house style for client work, set that once as a standard for everybody.
Analysis and English prose are two different skills
Treating them as one is how a strong analyst ends up owning slide formatting.
A first draft can need real editing while the thinking behind it is the best on the team. Those facts are unrelated. But the draft is the visible artifact, so the team recalibrates—smaller sections, more support work—and within three weeks the sharpest analyst is doing production.
Name the two stages separately:
- Draft for content. No first pass is judged on prose. Own the analysis, get it down, hand it over.
- Language pass. Whoever writes the cleanest English—native speaker or not—edits everyone's sections. A scheduled stage with a deadline, not a favor anyone asks for.
Two rules keep it honest. The pass covers every section, so nobody's work is singled out as the one that needed help. And it never becomes an argument for shrinking anyone's analytical scope: editing is a cheap fix applied at the end, which is why it shouldn't reshape who does the thinking.
Who presents, and why the fluent default is usually lazy
Sometimes the most fluent speaker should present. Live Q&A from a professor who interrupts is a different skill, and thirty minutes before a graded presentation isn't the moment for a development opportunity.
But defaulting to whoever speaks most easily hands one person ten weeks of visible work—which shows up in grades, in recommendations, and in what everyone remembers about who carried the project. It's often worse on the merits: a presenter who doesn't know the analysis cold fails the first hard question, and fluency won't rescue that.
Rehearsal closes most of the gap. Two full run-throughs out loud—not silent read-throughs—plus a written list of the four or five likeliest questions with answers drafted in advance. Prepared answers are a technique every consultant uses, not a crutch. Split the roles if it helps: whoever built the model presents it, open-ended Q&A goes to whoever improvises comfortably. Decide, don't default.
Peer evaluations: quiet is the most misread signal
This is where the whole thing converts into a grade.
"Didn't contribute much in meetings" is the most common unfair line in MBA peer evaluations, and it usually measures the meeting's structure rather than the person. Check the record. What did they produce? Did their written input change a decision? Was their analysis solid and on time? If yes across the board, what you observed is that your team runs fast meetings.
Evaluate contribution and delivery. Airtime is a proxy for neither, and once you've seen it, it's hard to unsee how much peer-evaluation vocabulary just measures who talked.
If you're the one doing this in your second language
Four things within your control, none of which requires becoming a different person in meetings.
Ask for the agenda in advance. Not as an accommodation—as a request that makes the meeting better. "Can you send the questions the day before? I'll come with a position." Nobody says no to that.
Put the substantive point in writing first. Post your analysis to the team thread before the meeting. Now it's on the table and can't be talked over, and the meeting becomes a discussion of your point instead of a race to introduce it. It also changes how the team reads you, because writing is where quality is legible.
Say "let me finish the thought." Five words, completely unremarkable, and native speakers say them to each other constantly. Not confrontational, and no apology needed in front of it.
Ask for the plain version. "What does that mean in plain English?"—about an idiom, an acronym, or a hedged instruction. Half the room wanted to ask.