Should I learn the cultural norms of each nationality in my team?

Some background helps you avoid obvious missteps, but a list of national traits used as a guide to individuals does more harm than good. Two colleagues from the same country can differ more than two from opposite ends of Asia. Use the background to form a question, then check it with the person.

Isn't it risky to talk about cultural differences openly in the team?

It is riskier to leave them unspoken, because they get discussed anyway, in smaller groups and less charitably. The safe way to raise them is through how the team works — how we decide, how we flag a problem — rather than through who comes from where.

What if the friction is really between local and foreign colleagues?

Then treat it first as a question of fairness and transparency: how work is allocated, who gets which opportunity, and on what basis. Perceptions of favouritism take root where those decisions are invisible. Making the criteria visible removes most of the fuel; what remains is for a direct conversation, and sometimes for HR.

Managing a multinational team that shares one language

Managers who arrive in Singapore from a single-culture workplace often say the same thing after a few weeks: the team is easier than they expected. Everyone speaks English, meetings run smoothly, nobody seems lost.

A few months later the picture is less simple. Deadlines were understood differently. A problem that one person flagged clearly — in their own terms — was not heard as a problem at all. Two colleagues who never argue in meetings have stopped working together.

None of this is about language in the narrow sense. It is about everything the shared language makes it easy to overlook.

Fluency is not alignment

When a team visibly struggles to understand each other, people check. They repeat, they write things down, they ask. When everyone is fluent, nobody checks, because there is no obvious reason to. That is why the most fluent multinational teams are often the ones where misunderstandings run longest before anyone notices.

The same sentence can be read three ways in the same room. “Let’s try to have it by Friday” is a firm commitment to one colleague, a hope to another, and a polite way of saying “not urgent” to a third. Nobody mistranslated anything.

Four gaps that survive a shared language

Hierarchy: who speaks first, and who speaks at all. For some colleagues, disagreeing with a senior person in a meeting is part of doing the job well. For others it is a breach of respect that they would only consider one to one, if at all. Both are normal; a meeting run as if only one of them existed will hear only half the team. The mechanics of that are covered in a separate article on the yes that does not mean yes.

Directness: what counts as clear, and what counts as rude. Feedback that one person experiences as refreshingly straightforward, another experiences as a public humiliation. The reverse is just as costly: a carefully softened correction that the recipient simply does not register as a correction. Adjusting the delivery without diluting the message is a skill, and it is the core of Self-awareness and positive communication.

Time: what a deadline means. A date can be a commitment, a target or an opening position. Teams rarely say which, and each member fills the gap with the convention they grew up with professionally.

Bad news: who delivers it, and how. In some working cultures a problem is raised the moment it appears. In others it is raised only once there is a solution to go with it, or passed upward through someone more senior. A manager who has not made the route explicit discovers problems late — and often concludes, wrongly, that someone was hiding them.

Passports are a poor guide to people

The temptation, once these gaps are visible, is to map them onto nationalities. It is the wrong move. The variation inside any one nationality is far larger than the averages suggest, people who have worked in several countries carry several rulebooks at once, and colleagues quickly notice when they are being managed as a stereotype.

A more reliable reading grid is working style. Tools such as DISC give a team a way of describing its friction in terms of how people prefer to decide and communicate — which is usually more accurate than nationality, and always less charged. The one-day DISC course is built for exactly that use.

What a manager can actually put in place

None of this needs a cultural briefing. It needs a handful of explicit rules, agreed with the team and written down:

How we disagree. For example: objections are written before a decision is discussed, and the senior person speaks last.
What a date means. “By Friday” means delivered by Friday at 6 pm unless someone says otherwise by Wednesday.
How a problem is raised. Early, to whom, and with or without a proposed fix.
How a decision is checked. Two people restate it in their own words before the meeting closes.

Add one practical habit: plan the team’s calendar with every relevant festival and public holiday in front of you, so that no one has to ask for an exception for something that should never have been one.

One language, many rulebooks: what a shared English hides in a Singapore team