Letter 4: The Translator

Hi friend,

Quick question: have you ever been in a meeting where the words coming out of someone's mouth turned into frantic, high-speed jazz? Bee-doo-bap-ba-doo-bop-skiddly-bop.

You smile. You nod. You say "sounds good." And you leave with no idea what you just agreed to.

You are not alone, and it is not your fault. I have spent my whole career standing in the middle of those moments. In learning and development, I stood between administrators and dining staff. In events, I stood between the host and the vendors. In advertising, I stood between the creative team, the web team, and the client. By the time I became Director of Traffic and Operations, being the bridge between departments was the literal job description.

What that taught me: most of the problems I fixed were not problems with the work. They were problems with the handoff.

Here are the five gaps I saw most often.

  1. Jargon. Every industry has its own shorthand, and websites are practically their own language. Explain it the way you would to a smart friend in a different field.

  2. Clashing communication styles. A detailed email does not replace a conversation. Some people need to hear things out loud so they can ask questions as they go.

  3. Assumptions. We get comfortable in our own topic and make leaps that feel obvious to us. Slow down, fill in the gaps, and meet people where they are without making them feel small.

  4. Not enough questions. Good communication starts with curiosity. Ask questions from every angle until you understand what someone needs and can give them a clear, concise explanation.

  5. Too many words. Get to the point first, then expand as needed. Extra context and rabbit holes can leave the other person more confused than when you started.

Recognizing these gaps is one thing. Knowing how to bridge them is another.

Three skills make the difference.

Know your audience. The administrator, the dining staff, the client, and the developer all need different things from the same message. Before you explain anything, ask yourself what the person in front of you already knows and what they need to walk away with. If you are not sure, ask them.

Pay attention. The best translators do not wait for someone to say "I don't understand." Most people never will. They nod, they go quiet, or they say "sounds good" while their face says otherwise. Listen to what is said, notice what is not, and watch body language: eyes drifting, crossed arms, a polite smile that does not match the moment. Then step in early.

Build trust. People are much more likely to admit they are lost when they feel safe. Nobody wants to look unknowledgeable in front of the people they are trying to impress. Explain things in the moment, then follow up one-on-one afterward, where the real questions tend to come out. And be direct, but kind about it.


Let me show you what all three look like together.

I once worked with a client who needed a new website. Their team had never managed one before, and each person came from a different department with a full-time job on top of this project. They were smart people, and they approached it with humility, grace, and dedication. They were one of my favorite clients.

But every time we hopped on a call with the web team, I watched their eyes go wide.

Picture walking into an unfamiliar building and asking one simple question: "Where is the bathroom?" Now imagine the person you asked starts explaining the plumbing, the pipe materials, and turn-by-turn directions through the whole building. They are an expert, and everything they say is accurate. It just isn't what you asked. On those calls, my job was to say, "It's down the hall on the left," and save the plumbing for when someone asks.

It is easy to miss. When you are used to speaking a language, it is hard to notice that someone has not quite caught up. That is not carelessness. It is what happens when you live inside your own field.

Because we had years of trust between our teams, one or two of them felt comfortable asking questions. The others each owned a piece of the project they did not feel confident about. For them, I asked questions tied to their part:

"Which page on the site will your department touch the most?"

"What is the first thing a visitor should be able to do on your page?"

"What do your customers ask you about most often?"

Questions like these can't be answered with a nod. They walked each person through the process, so their needs were met before anyone had to admit they were lost.

I never asked, "What questions do you have?" They did not know what they did not know, and that was not their job. It was mine.

When a message is not landing, the answer is rarely more words. It is usually a different word, a better question, or noticing that someone needed help before they asked.

Now I have a question for you: where does a message get lost most often on your team or in your projects? Email me at katie@papermoonconsult.com or message me on social at @papermoonconsulting, and tell me in a sentence or two. I read every message, and I will write back with a thought or two on what might help.

And if you feel like your team needs a translator, let's talk about what is going on and how we can fix it.

Until next time,

Katie

Next
Next

Letter 3: More Than A Logo