Вставляє палки в колеса.
One phrase. Four words. And the moment you say it, the other person immediately understands: the frustration, the pattern, the relationship dynamic, exactly who keeps doing it and why it matters. No explanation needed. The whole picture, delivered at once.
Now try saying that in English.
Not translating it — saying the whole idea, the frustration, the history, the subtext, out loud, in English, while the conversation is still happening.
In a meeting. To your manager. When you’re already a little tense and the conversation is moving faster than you’d like.
You know what’s happening. Someone is blocking the process, making things harder than they need to be, creating obstacles on purpose. You know this clearly. But the phrase isn’t there fast enough. So what comes out is something like:
“He makes it difficult for the team. He doesn’t really cooperate.”
It’s not wrong. It’s not bad English. But it’s not what you meant either. It’s a lighter version. A safer version. The real thought — the one with the frustration and the context and the years of watching this particular dynamic — stays somewhere in the gap between what you think and what you can say. Not said, not heard.
This is the moment people describe to me as “my English disappears.”
It doesn’t disappear. It gets compressed.
Here’s what’s actually happening.
When your idea is simple — giving an update, confirming a plan, responding to a direct question — your English holds up well. You find the words, build the sentence, say the thing. It works.
But when the idea becomes complex, the situation changes. Complex means: layered, emotional, uncertain, politically sensitive, or just — big. The kind of idea you’d normally talk through over coffee in your first language, where you can take your time and use all the words you have.
In those moments, your brain is doing several things simultaneously. It’s holding the full thought (the situation, the history, the people involved, what you actually want to say). It’s managing the tone (not too direct, not too soft, professional but honest). And it’s searching for English — the right words, the right structure, the right register for this particular person and context.
That’s too much. Something has to give up. Usually, it’s the English.
Your brain protects the idea and simplifies the language. So what comes out is a reduced version: accurate enough, but missing the nuance, the weight, the full truth of what you wanted to say.
Linguists sometimes call this the cognitive load problem. You can think of it more simply: when the idea is big, your English gets squeezed.
Why this happens more in English than in your native language
In your first language, you’ve been building your vocabulary and phrase library your entire life. You have expressions for almost everything — for frustration, for irony, for the kind of situation where someone is technically doing their job but making everyone’s life harder. You don’t have to build meaning from scratch. You reach for it, and it’s there.
In English, that library is smaller and less practiced. Not because you don’t know English — you do. But because you haven’t yet built the phrases for the specific ideas you carry: the work dynamics, the interpersonal tensions, the nuanced opinions about how things should be done and why they aren’t.
Take this example:
тягну час
If you say this to a Ukrainian colleague, they immediately know: you’re stalling, you know you’re stalling, you’re maybe a little embarrassed about it but also a little strategic. One phrase holds all of that at once.
In English you’d need to choose: I’m stalling (blunt, a little confessional), I’m buying time (more strategic, deliberate), I’ve been dragging my feet (honest, slightly self-deprecating). These aren’t translations. They’re different framings of the same reality, each carrying a slightly different shade of meaning.
To choose the right one in real time, under pressure, while the conversation is happening? That’s not a vocabulary problem. That’s a library problem. You haven’t yet built the collection of phrases for the ideas you actually need to express in English.
What this looks like in practice
You’re in a meeting. Your manager asks how you feel about the current project structure.
What you want to say: the setup is creating a bottleneck, one person has too much sign-off power, the team is frustrated, and you’ve been watching this pattern repeat itself for six months.
What comes out:
“It’s a bit slow. Maybe we could improve the process.”
Afterwards, you think: that’s not what I meant. I should have said more. I didn’t explain the real problem.
Or: you’re talking to a colleague about a difficult team dynamic. You see the issue clearly. You could describe it in your first language in thirty seconds. In English, you start, feel the words slipping, notice you’re translating in your head, worry you sound unclear — and say something like:
“I think there’s some misunderstanding between them.”
Then you move on, leaving the real thought unsaid.
These moments accumulate. Over time, you notice that your English self is somehow smaller than your real self. Quieter. Less precise. Less like you.
That gap — between who you are and who you can be in English — is exactly what this is about.
What actually helps
The instinct is to learn more vocabulary. And vocabulary does matter.
But learning more words in general won’t close this specific gap, because the gap isn’t general. It’s in the phrases for the ideas you carry — the ones that are specific to your work, your context, your way of seeing things.
What actually helps is building those phrases deliberately, through the situations you actually face.
This looks like: taking a real conversation where your English felt weak or thin, and going back to it. What did you want to say? What came out instead? What’s the phrase that would have carried the real meaning?
Sometimes you find it yourself. Sometimes you need someone to offer it to you at the right moment — the way a teacher might hear you struggling to describe a situation and simply give you the exact phrase for it — and suddenly it lands, because you just felt the need for it.
That’s how the library grows. Not through lists, but through real moments of expression, where you’re trying to say something specific and you find (or are given) the exact language for it.
This is also what makes it hard to turn passive vocabulary into active — the words are there, but they haven’t been used in a real moment yet. This post explains why that gap exists and what actually closes it.
The other thing that helps is permission: to stay with the complex idea even when the English feels imperfect.
The instinct under pressure is to simplify: to say the easier, safer thing and move on. But every time you do that, you confirm to yourself that your English can’t hold the real thought. And it becomes a little harder to try next time.
Staying with the idea — even haltingly, even imperfectly — is how you eventually stop having to.
A few phrases worth keeping
You’ve seen three Ukrainian expressions in this post, each with an English equivalent. That’s already the first step: you recognized them in context. Here’s the second: try using them.
- Вставляє палки в колеса — in English, to throw a spanner in the works, or more casually, to get in the way or to create obstacles. Think of someone at work who does this. Can you describe the situation in two or three sentences?
- Тягну час — in English: to stall (the other person can usually tell), to buy time (more deliberate and strategic), or to drag your feet (honest, a little self-critical). Which one fits the last time you avoided a difficult conversation?
- Несу команду на своїх плечах — in English, I’ve been carrying this team. Think of a situation where you felt this. Can you describe it in English — not the simplified version, but the real one?
You don’t need to get it perfect. You just need to stay with the idea long enough to say something true.
Sound More Like Yourself in English
