VOCABULARY IS
THE BARRIER

I couldn't start a GitHub repo without learning what a repo was. Not conceptually. Literally. I couldn't type the right words into the right fields because I didn't have the vocabulary to make what I needed tangible to the system or to the people who ran it.

This is not a metaphor. This is what it actually feels like to be competent, experienced, and completely locked out of a conversation because you don't speak the language yet.

Most people assume communication problems are about tone or timing or politics. They're not. They're about vocabulary. If you can't name what you need in the language the other side uses, you don't exist to them. Not because they're gatekeeping. Because they literally cannot hear a request they don't recognize the shape of.

The most important communications work I've ever done looked like project management. An enterprise naming convention project. The full-stack engineers needed a standardized naming system across the organization. They understood why it was critical and why it was difficult. I didn't. So before I could do anything useful, I had to learn their language well enough to understand the problem from the inside. Not summarize it. Understand it the way they did.

Then I had to turn around and explain it to every non-technical team in the building. People moving at full speed on their own priorities who had no patience for engineering jargon. I had to translate without diluting. Simplify without lying. It felt like being a foreign correspondent in my own company.

Nearly a decade and a half in broadcast journalism trained this instinct without giving it a name. Every day was translation. Take the complicated thing, understand it well enough to be honest about it, then explain it so someone with no background still understands why it matters. The vocabulary was always the barrier. Not the audience's intelligence. Their access to the right words.

The career pivot made it obvious. I watched brilliant technical specialists fail to get AI adoption. Not because the tools were bad. Because nobody could bridge the vocabulary gap between what the technology does and what the average employee needed to hear to trust it. The implementation spoke one language. The workforce spoke another. Nobody was translating.

Communication isn't decoration on top of the real work. It's the mechanism by which the real work becomes possible.

They're listening. They just can't hear you yet.