Ask a senior non-native professional how their English is and they'll say "fine," "pretty good," "I manage." They won't say "I froze on a word in a board meeting last week and it cost me credibility." They won't say "I've been quietly avoiding certain words for three years because I'm not sure they'll land right." They won't say "I know exactly what the problem is and I haven't told anyone."
I know this because I was that person. And when I started building Lyra Practice and talking to the people it was built for, I found the same silence everywhere.
It's not the silence of not knowing. It's the silence of knowing exactly what the problem is and choosing not to name it out loud.
Why it doesn't get named
Naming a language difficulty at a senior level feels professionally risky in a way that's hard to overstate. You've spent years building credibility. You've been hired for your expertise, your track record, your judgment. You're the person other people come to for answers. Saying "I have a vocabulary activation problem" feels like handing someone a reason to see you as less capable than you are — like a crack appearing in something you've carefully maintained.
So you don't say it. Instead, you find other ways to describe what's happening.
"I'm more of a written communicator." True, possibly. Also a way of explaining why you're quieter in meetings than your written work would suggest.
"I'm not assertive enough in English-language settings." Also true in some sense. But the reason for the quietness isn't personality — it's that the precise word doesn't surface in time and you've learned not to speak until you're sure.
"English isn't my first language so I prefer to listen more." Reasonable-sounding, widely understood, socially acceptable. And a way of making a systematic pattern look like a personal preference.
All of these are true in some sense. None of them name the actual thing.
The management strategies
What you do instead of naming it is manage around it. And the management strategies are worth naming specifically, because anyone who has lived this will recognize them.
You avoid certain words in meetings even though you'd use them without hesitation in an email. You let a native speaker colleague make the point you were about to make, because they'll phrase it more fluently and the outcome is the same. You steer conversations away from topics where you're less confident in the register. You over-prepare for presentations — scripting the precise language in advance so you don't have to produce it live. You ask for things in writing when you could ask verbally, because written English gives you the time that spoken English doesn't.
These are intelligent adaptations. They've worked. They've protected your credibility in the moments that mattered. But they have a cost: they've also placed a ceiling on how much you contribute, how loudly you're heard, and how often you're in the room for the conversations that matter most. The language ceiling isn't always something imposed from outside. Sometimes it's something you've quietly constructed yourself, one strategic avoidance at a time.
The part nobody talks about
Here's what makes the silence exhausting in a way that's hard to explain to someone who hasn't experienced it: not naming the problem doesn't make it invisible to you.
You're aware of every substitution. Every time you said "important" and meant "consequential." Every time you restructured a sentence to avoid a word you weren't sure would land. Every time you watched a native speaker colleague use exactly the phrase you needed and felt the gap sharply. The silence is entirely external. Internally, you're carrying a running awareness of it — a kind of low-grade cognitive overhead that's always present in English-language professional contexts.
The gap between that internal experience and the "I manage fine" you tell people when they ask is significant. And maintaining it over years takes more energy than the problem itself would require to fix.
What naming it actually does
The gap doesn't get smaller by not talking about it. It gets smaller by treating it as what it actually is: a specific, technical problem with a specific, technical cause.
As the research on vocabulary acquisition makes clear, this isn't a fluency problem, a confidence problem, or a personality problem. It's an activation problem — the gap between words that exist in passive vocabulary and words that are reliably available under pressure in real professional contexts. That's a solvable problem. And solving it doesn't require admitting anything to anyone.
You can work on this privately. Systematically. Before the next high-stakes meeting, not after it. The words that keep collapsing under pressure are identifiable. The practice that moves them from uncertain to automatic is understood. The only thing the silence accomplishes is delaying that work.
I built Lyra Practice for this specifically — because the problem is real, the silence around it is understandable, and neither of those facts makes it less worth fixing. There's a free tier if you want to start without telling anyone you're starting.