Your Employees Don't Need Another Language Course. They Need to Speak in Meetings

An employee can score B2 in German and still say almost nothing in Monday's team meeting.

That's not a contradiction. It's what happens when a company measures the wrong thing. Proficiency tests what someone knows under calm, structured conditions. A meeting tests something else entirely: whether they can produce that knowledge in real time, while someone is talking over them, under a deadline, and in front of people whose opinion of them actually matters.

This gap isn't specific to German. It can show up in any working language. And it's why a completion certificate rarely predicts who will actually speak up when the conversation gets fast.

The gap between proficiency and performance

Most corporate language programmes report proficiency: a CEFR level, a completion certificate, a test score. None of these measure what actually happens in a meeting. An employee can read a contract fluently, write a clear email, and still take three extra seconds to respond when a colleague asks an unscripted question, three seconds that, in a live conversation, read as hesitation, uncertainty, or worse, disengagement.

This gap is well documented in second language research, not just anecdotally observed. Our guide to the science behind the Speaking Gap™ covers the research in depth. The short version: understanding a language and producing it under pressure draw on genuinely different cognitive processes, regardless of which language is involved, and a course that only trains one doesn't automatically train the other.

What "proficiency" actually measures

CEFR proficiency tells you a great deal about language ability. What it cannot fully reproduce is the speed, interruption, social pressure, and unpredictability of a real workplace meeting.

What proficiency testing measures	What a meeting actually demands
Comprehension with time to process	Comprehension in real time, often while multitasking
Grammatically accurate production	Fast, imperfect production that still gets the point across
A structured, predictable format	Interruptions, cross-talk, and topic changes with no warning
Individual performance, no social stakes	Performance in front of colleagues whose perception matters

None of this means proficiency testing is worthless. It means it answers a different question than the one HR actually needs answered: whether an employee can hold their own in the room, whichever language that room runs in.

Meetings: Where the gap shows up first

Meetings are usually the first place this gap becomes visible to a manager, because they're the first setting where language has to work under social pressure rather than academic conditions. An employee who writes confidently in a second language often goes quieter than colleagues in meetings, not because they have less to contribute, but because meetings punish hesitation in a way written communication never does.

This has a real organisational cost. Employees who stay quiet in meetings are read as less engaged, less senior, or less confident, regardless of what they actually know. The company isn't only losing language performance. It may be losing ideas, expertise, and decision-making input from employees it hired precisely for those things.

Over time, that perception compounds: quieter employees get asked for input less often, which gives them less practice speaking up, which reinforces the original pattern. A language course that never touches meeting dynamics directly does nothing to interrupt that cycle, no matter which language the meeting runs in.

Interruptions: The moment most training doesn't prepare you for

Almost no structured language course trains for interruption, because it's hard to script and doesn't fit neatly into a workbook exercise. But interruption is one of the most common features of real meetings: someone jumps in mid-sentence, a tangent gets raised, the original point has to be picked back up a minute later without losing the thread.

In a first language, recovering from an interruption is close to automatic. In a second language, it often means starting the sentence-construction process over from scratch, mid-conversation, while everyone else has already moved on. This is one of the clearest places where "I understand everything being said" and "I can hold my own in this conversation" turn out to be entirely different claims.

Retrieval speed: Why knowing a word isn't the same as producing it in time

There's a specific mechanism behind this, and it's worth naming directly rather than treating it as vague nervousness. Speech production, as described in Willem Levelt's influential model of language production, moves through distinct stages: conceptualising what to say, formulating it linguistically, then articulating it aloud. In a first language, this process is largely automatic. In a second language, each stage takes measurably longer, and re cent research on second language acquisition confirms that speaking demands fast lexical retrieval, with L2 learners facing cognitive demands that limit the attentional resources available to find the right words in real time.

This is why an employee can recognise a word instantly while reading and still fail to produce it quickly enough in live conversation, whether that word is German, French, or English. Recognition and retrieval are different skills, and most vocabulary-heavy courses train the former far more than the latter.

Confidence: The variable most reports don't track

Even accounting for retrieval speed, confidence shapes how much of that ability actually gets used. Two employees with identical vocabulary can perform very differently in the same meeting, because confidence determines whether someone attempts to speak at all, not just how well they do once they start.

Standard training reports don't measure this, because it doesn't fit neatly into a CEFR level or a completion percentage. Instead, it shows up as a pattern HR can observe directly: who volunteers information unprompted, who waits to be asked, who visibly hesitates before answering a direct question. None of that is captured by a certificate.

What practical communication actually requires

Put these pieces together and a clearer picture forms. Practical workplace communication requires fast retrieval under real cognitive load, the ability to recover from interruption without losing the thread, and enough confidence to attempt a response before someone else fills the silence.

This is also why the fix isn't more course content. It's different practice: live, unscripted, time-pressured conversation, repeated often enough that retrieval speeds up, and confidence builds alongside it.

For teams working specifically in German, our guide to German for work in Switzerland covers what this looks like in specific workplace situations, meetings, email, and the small talk that trips people up in between, though the same underlying mechanism applies regardless of the working language.

How XLINGUA addresses this, in any language

XLINGUA Flow™ is built around this exact mechanism, and it's applied the same way across all six languages XLINGUA teaches: German, Swiss German, English, French, Italian, and Spanish. As XLINGUA has noted publicly, German remains the most requested language, but the same speaking-first method applies without modification to every other language taught, since the underlying gap between understanding and producing isn't language-specific.

Sessions run in small groups with 70 to 80 per cent speaking time, deliberately including the kind of unscripted, interrupted, real-time conversation a structured course usually avoids, because that's specifically what builds faster retrieval and lower-pressure confidence. Corporate programmes go further, using industry-specific content so the practice resembles the actual meetings employees walk into, in whichever language their team actually works in.

Conclusion

A language course measures what someone knows. A meeting measures what someone can produce, under pressure, without a script, while someone else is already talking. These are related skills, but they aren't the same, and a training programme that only tests the first will keep producing employees who pass every assessment, in any language, and still go quiet in the room that actually matters.

If your employees pass the level test but disappear in the meeting, you don't have a proficiency problem. You have a Speaking Gap™.

Let's connect and find out where it is costing your team performance.

Frequently asked questions

1. Why does an employee with a high CEFR level still struggle in meetings?

CEFR levels measure comprehension and production under calm, structured conditions. Meetings demand fast retrieval, recovery from interruption, and confidence under social pressure, none of which a standard proficiency test measures directly, in any language.

2. Does this gap only apply to German, or to other languages too?

It applies across languages. The mechanism, comprehension and production drawing on different cognitive processes, isn't specific to German. It shows up the same way in French, English, Italian, or Spanish workplace communication.

3. What is retrieval speed, and why does it matter for workplace communication?

Retrieval speed is how quickly a speaker can access and produce a word or phrase they already know. In a second language, this process takes measurably longer than recognition alone, which is why someone can understand a word instantly while reading but still hesitate to produce it in live conversation.

4. Can confidence really affect language performance if the vocabulary is already there?

Yes. Confidence determines how much of a person's actual language ability comes out in the moment, since hesitation and avoidance can prevent someone from attempting a response at all, regardless of whether they know the right words.

5. What should companies actually train for, if not proficiency?

Fast retrieval under real conditions, recovery from interruption, and confidence to speak without a script, all of which require live, unscripted practice rather than more vocabulary or grammar instruction, whichever language the team works in.