Offshore Compass

Managing offshore teams

"Yes" doesn't mean "understood": managing an offshore team across cultures

Last checked: October 30, 2026

You explain the task. Your new team member in Manila, Bangkok or Ho Chi Minh City nods and says yes. Two days later the work comes back wrong, or doesn't come back at all. This page is about that gap, and a few simple habits that close it.

The short version

  • A "yes" can mean "I heard you," "I don't want to make this awkward" or "I'll figure it out later," not "I understand and agree."
  • "Do you understand?" is a weak check. A US government plain-language toolkit warns that people are likely to answer "yes" to it whether they understand or not. [S1]
  • Ask people to explain the task back in their own words, in small chunks, and send a short written recap afterward. [S1]
  • Expect some candidates and new hires not to show up, and plan your hiring around it.
  • Rules of thumb help you start. They don't replace getting to know the people you work with.

Why "yes" isn't always yes

René Anant Feddersen grew up in Thailand, studied and worked in Europe and the US, and started his first company in Bangkok in 1998. Looking back on that time, he writes:

"People would nod in agreement, but as I came to understand, this neither meant that they agreed with what I was saying, nor that they understood my meaning." [S2]

Writing about Bangkok today, almost 30 years later, he says many things have changed, but "People still nod in agreement when they don't understand what is being said." [S3]

That's one person's experience in one country, and he is careful to say so. But any manager who has worked across cultures will recognize the pattern: in many workplaces, saying "I don't understand" to a new boss, in front of others, feels like a bigger risk than saying yes.

Check understanding without putting people on the spot

These techniques come from AHRQ's teach-back tool, written for doctors explaining instructions to patients. They work the same way for a manager explaining a task. [S1]

  • Ask for a teach-back, not a yes. "Just so I know I explained it well, how would you describe the next step to the team?" You're checking your explanation, not testing them. [S1]
  • Avoid yes/no checks. Skip "Does that make sense?" and "Any questions?" [S1]
  • Chunk and check. Explain one piece, ask for a teach-back, then move on. Don't save it for the end of a long call. [S1]
  • Re-explain differently. If the teach-back is off, explain it another way and check again. If someone just repeats your words back, they may not have understood. [S1]
  • Use "show me." For a process (a tool, a report, a system), ask them to do it while you watch, screen shared. [S1]

Make it easy to say "I'm not sure"

  • Follow every call with a short written recap: what, who, by when. Ask them to reply with anything that's different from what they understood.
  • Ask for ideas one-on-one before the group call. René says mid-level staff in Bangkok today "can and want to participate in developing solutions," but are less likely to present their ideas "if senior people are in the room." [S3]
  • Give a safe way to flag problems early: a standing question in one-on-ones ("What's unclear or stuck this week?") works better than waiting for someone to volunteer bad news.
  • Thank people for questions, especially the first few. It tells the whole team that asking is normal.

Why candidates check with family before accepting

When a Filipino candidate says they need to talk with family before accepting your offer, they aren't hesitating. A new job often affects more than one person. It can change shared household finances, who handles caregiving, and the daily schedules of several family members. Talking it through at home is part of making a careful decision.

You can make that conversation easier. Put the offer in writing and state clearly the pay, benefits, working hours, leave and employment status. An offer that's easy to explain at home gets a faster, firmer yes.

Plan for no-shows when hiring

René's observation from Bangkok: people now leave jobs without notice less often than in the late 1990s, but "applicants consistently schedule a job interview and then fail to show up for it," and new hires sometimes accept an offer and don't show up for work. He says this is more common for line and supervisory roles than for managers. [S3]

Whether or not that matches your market, it's cheap to plan for:

  • Keep two or three finalists warm until your hire's first day.
  • Confirm interviews and start dates the day before, by the channel the candidate actually uses (often chat, not email).
  • Make the first day easy to say yes to: a named person to meet, a clear schedule, equipment ready.
  • If you hire through an employer of record, ask how it handles no-shows and replacements. Compare providers on our EOR page.

Rules of thumb vs getting to know people

René describes two approaches. One is the "apply-the-format" path: etiquette guides, do's and don'ts, cultural rules of thumb. The other is learning "one interaction at a time" through relationships. He calls the usefulness of cultural theory "overstated," and is clear that this "is firmly in the domain of opinion." [S2] He also accepts that the two paths aren't mutually exclusive: rules of thumb suit people who move posts often, while immersion pays off over a longer stay. [S3]

For a manager running a team from another country, a reasonable middle path:

  • Use the habits above from day one. They work in any culture, including your own.
  • Treat any "cultural rule" you read as a hypothesis about a group, not a fact about the person in front of you.
  • Spend real time on one-on-ones in the first 90 days. That's where you learn how each person signals "yes," "maybe" and "no."

Next steps

  • Working across time zones too? See our time zones guide for overlap hours.
  • Compare employer-of-record providers on the EOR page.

Sources