What multilingual team leadership taught me about clarity

A front desk in Waikiki is one of the most multilingual rooms you will ever stand in. On any given shift the guests arrive carrying half a dozen first languages, and so does the team behind the desk. Someone grew up speaking Tagalog at home, someone else Japanese, someone else a language of the mainland, and English is the shared floor we all stand on together even though none of us stands on it in quite the same way. I learned early that leading in that room is not about being the best speaker of anything. It is about making sure understanding actually happened, which turns out to be a different job entirely.

I carried that lesson from Waikiki to rooms operations in San Francisco, another city where a team and its guests hold many languages at once. And the more I led across those gaps, the more I realized the skill I was building was not really about language at all. It was about clarity. When you cannot assume a shared shorthand, you stop pretending that saying a thing is the same as landing it. That habit, once you build it, makes you a better leader in your first language too.

Fluency is not the requirement. Clarity is.

The first thing to unlearn is the idea that you need to speak every language on your team to lead it. You do not, and believing you do will paralyze you. Some of the best floor leaders I have worked alongside were people with one strong language who led a team of many, and they did it by being unusually clear and unusually patient. They said the essential thing simply, they checked that it arrived, and they never mistook a polite nod for comprehension.

Because that is the trap. In a room full of first languages, agreement is cheap and understanding is not. A tired agent at the end of a shift will nod at an instruction they only half caught, not out of dishonesty but out of courtesy and fatigue. If I take the nod at face value, the task goes undone and I blame the person, when the real failure was mine for confirming nothing. So I built a habit of closing the loop: tell me what you are going to do, in your words. Not as a test, but as a courtesy that protects us both.

In a room full of first languages, agreement is cheap and understanding is not.

That single habit, asking someone to say the plan back, changed my leadership more than any technique I have learned since. It slows things down by ten seconds and saves the shift an hour. And it does something quieter too. It tells the person that I care whether my meaning reached them, which is a form of respect they feel long before they could name it.

I want to be honest about where this started for me, because it did not start with a management book. It started with my own name. Yiyuan is not a name most guests reach for easily, and long before I led anyone I stood on the other side of a language, watching people decide whether my effort to meet them in theirs was worth their patience. That memory sits under everything I do as a leader. I know what it costs to work in a language that is not the one you dream in, and I know how much a small act of patience is worth to the person receiving it. You lead differently once you have needed that patience yourself.

How do you give feedback across a language gap?

Feedback is where a language gap gets dangerous, because feedback lives in nuance, and nuance is the first thing lost across languages. The abstract managerial phrases we lean on, take more ownership, be more proactive, raise your energy, mean almost nothing to someone translating in real time, and worse, they can land as vague criticism the person cannot act on. The fix is the same discipline that makes all feedback better, just enforced harder: be concrete.

Instead of be more attentive, I say, when a guest walks up, look up and greet them before they reach the desk. That is a picture, not a concept, and a picture crosses a language gap intact. Then I ask the person to tell me what they will do differently, and I listen to the answer for meaning, not for grammar. If they describe the right behavior back to me, the message landed. If they describe something else, I have learned that gently, without either of us losing face, and I can try again with plainer words.

Small choices that keep feedback clear

• Trade abstractions for actions. Describe the observable thing you want to see, not the quality you want them to have.
• Confirm, do not assume. Ask for the plan in their words. A nod is not confirmation.
• Slow your pace, not your respect. Speaking simply is not the same as speaking down. Keep the dignity, lose the jargon.
• Correct meaning, never accent. Never let a person feel their command of English is what is being judged. Judge the work, protect the person.

This is also where standards and language meet. A standard that lives only as a paragraph in a handbook will not survive translation. A standard shown, demonstrated on the floor and confirmed in plain words, will. That is one reason I lean so hard on modeling over memos. The point of building service standards that stick is that the team keeps them on their own, and a team keeps what it genuinely understood, not what it was handed on a page it half followed.

It helps to build a shared vocabulary on purpose. Over a few weeks, a good team lands on a handful of plain phrases everyone uses the same way: what we call a walk, how we say a room is not ready, the one word that means a guest needs a manager now. That shared shorthand is worth building deliberately, because it removes ambiguity from exactly the moments that move fastest. I would rather have five words the whole desk owns cleanly than a polished script half the team is quietly translating. The goal is not elegant language. It is language that cannot be misread when the lobby is full.

Serving the guest in their language, keeping the team included

There is a moment I love on the floor, and it is when an agent switches into a guest's own language and I watch the guest's shoulders drop. A traveler who has spent a long flight bracing for the effort of a second language suddenly does not have to brace. That is service at its best, and I would never dampen it. When an agent can meet a guest in their first language, I want them to do it every time it helps.

The leadership task around that moment is not to control it. It is to keep it inclusive. On a busy desk, a switch into another language can quietly leave a nearby teammate stranded, unsure whether they are still needed, unsure what was just decided about a guest they may have to help next. So the norm I coach is simple: serve the guest fully in their language, then give the team the one line they need in the shared one. The guest gets warmth, the teammate gets the thread, and nobody has to choose between the two.

Getting that norm to hold takes trust, because you are asking people to manage two audiences at once under pressure. That trust is built the same way it is always built, in small reliable moments rather than announcements. A team that knows you value their languages as an asset will extend themselves for the guest and loop the floor in without being told twice. Which is why the work of leading across languages and the work of building trust with a new team are really the same work. Respect for how someone speaks is one of the fastest ways to earn it.

A worked example: one instruction, confirmed

Here is the confirm-back habit in motion, because it is easy to nod at in the abstract and skip under pressure. A group of twelve was arriving at once and I needed an agent to hold three connecting rooms as a block and not release them to walkins. The lazy version is "keep 610 through 612 together for the group, okay?" and a nod. What I actually said was, "We've got a group of twelve landing in an hour. I need 610, 611, and 612 held as a block. Tell me back what you're going to do with those three rooms." The agent said, "Hold all three for the group, do not give them to anyone at walkin." That is confirmation. It cost ten seconds and it saved a scramble at arrival, because I knew the essential thing had landed rather than hoping it had.

Compare that to the shift where I skipped the step. I told a tired agent at hour nine to "comp the parking for 402 and note it on the folio," got the nod, and moved on. The parking got comped; the folio note never happened, so the next shift had no record and the guest was charged again at checkout. The agent had half caught it and been too courteous to say so. The failure was mine, not theirs, for confirming nothing. One missing question turned a thirty second task into a guest recovery two days later.

Concrete versus abstract, across a gap

Every concrete version is a picture, and a picture crosses a language gap intact where a concept does not.

What the gap teaches you about clarity everywhere

Here is the part that surprised me. Leading across languages did not just make me better with a multilingual team. It made me clearer with everyone, including people who share my first language exactly. Because once you have felt how easily meaning goes missing across a language gap, you stop trusting that it always arrives just because two people speak the same tongue.

The truth is that we overestimate shared understanding constantly, even in one language. Two people who both speak fluent English can walk away from the same instruction with two different plans, because words carry assumptions, and assumptions are invisible. The language gap simply makes that failure loud enough to notice. Once you have trained yourself to confirm meaning with someone translating in real time, you keep confirming it with everyone, and your whole team gets clearer instructions as a result.

It changed how I run a handoff and a preshift too. I stopped ending either one with any version of does that make sense, because the honest answer is always yes even when it is no. Instead I ask for the one thing that matters back, in the person's own words, and I listen for whether the essential piece survived the trip. That habit came straight from the multilingual desk, and it has made every briefing I give tighter, whatever language the room happens to share.

I have also learned patience from it, the useful kind. When a person is doing the work of a shift in their second or third language, they are carrying a load I am not carrying, and they are doing it while smiling at guests. That reframes a lot. What might read as slowness is often careful translation happening in real time. What might read as reserve is often the caution of someone making sure they get it right. When I remember that, I lead the person in front of me instead of the one I assumed, and I nearly always find more capability than I expected.

There is a bias worth naming here, because it is quiet and it is common. We tend to mistake fluency for competence. The agent who speaks fastest and most confidently in the shared language reads as the strongest, and the one who chooses words carefully reads as less capable, when often the opposite is true. Some of the most capable people I have led were the ones who spoke least, not because they knew less but because they were being precise across a gap the rest of us did not have to cross. A leader who only rewards the smoothest talker will quietly overlook half the room. Part of leading across languages is training your own ear to hear substance under an accent, and to promote for judgment rather than for polish.

None of this requires you to become a linguist. It requires you to hold two beliefs at once: that understanding is never automatic, and that the effort someone makes to meet you across a language is a strength worth honoring rather than a gap worth noting. Do that, and you will lead a multilingual team well even if you only speak one language yourself. The skill was never about how many languages you command. It was about caring enough to make sure the essential thing landed, and that is the whole of leadership, said in any tongue.