Trust Across Cultures: Building Real Connection in Distributed Teams
The silent week
Giulia Scalaberni's remote team went completely silent for a week after she asked "any questions?" during onboarding. Nobody spoke up. Nothing.
Many leaders read that silence the same way: no questions means people understood, so move on.
Giulia's team included people from Austria, Italy, and India, each bringing different cultural expectations about challenging authority, asking for help, or admitting confusion in front of a group. In some of those cultures, saying "I don't understand" in a full-team meeting reads as a public admission of weakness.
That's where good intentions and actual leadership come apart. A leader can sincerely want psychological safety and open communication and still build habits that silence the people who most need to speak. We cover the wider pattern in leading global teams across cultures.
What Erin Meyer's Culture Map tells you
Erin Meyer's book The Culture Map lays out how cultures differ in their approach to trust, communication, feedback, and decision-making. The framework is only useful if leaders change their practices because of it.
In high-context cultures, common across much of Asia and Latin America and parts of Europe, trust and psychological safety come from relationship first and explicit permission later. A manager asking "any questions?" at an all-hands is assuming a low-context norm: if you have something to say, say it. In a high-context setting, that question without any relational groundwork creates the look of openness while people stay quiet.
The three-question workshop
Giulia's fix was specific. She ran a three-question workshop during onboarding, with no work talk allowed. The questions let people introduce themselves as people first: Where are you from? What do you love to do outside of work? What's something you've learned recently that surprised you?
Icebreakers aren't magic. This one worked because it built relational permission before asking for professional honesty. People who know each other's names, where they're from, and what they care about are more likely to speak up when something's unclear, even in cultures where that cuts against the grain.
The takeaway is practical and testable. On distributed, multicultural teams, leaders build psychological safety through small, deliberate relational work done before they ask anyone to be vulnerable. Declaring it doesn't work, which is why culture starts with permission more than policy.
A decision rule that slows down urgency
Giulia runs her team across Europe and India with a principle she sums up as "everything urgent, nothing urgent really." The rule: any decision that feels urgent waits 24 hours unless it's a genuine safety issue.
You'd expect that to slow execution. In practice it speeds things up. Most urgency is emotional. A request feels time-pressured because of how it lands, while the clock isn't actually running. Holding decisions for a day separates real emergencies from noise and gives people across time zones a chance to weigh in before whoever's awake first decides. Giving people context before a decision is the same idea behind the lore block.
Across cultures, the rule also makes room for different communication styles. Some people prefer to give input asynchronously and in writing. Others prefer a live conversation. A 24-hour window gives both a chance to show up.
Trust as an operational responsibility
Giulia's advice to senior leaders is about operations: if your dishwasher doesn't show up, your whole restaurant has a bad night. The point holds well beyond the kitchen. Every person at every level, from a senior engineer to a junior analyst to whoever keeps the infrastructure running, is part of what makes the system work.
So leaders can't treat trust and psychological safety as optional cultural values. They're operational inputs. On a team where people don't feel safe raising problems, problems stay hidden until they break production or sink projects. Leaders who are new to a distributed team have to earn this deliberately, as we lay out in how new leaders build trust and credibility.
For distributed teams, that's the reason to invest. Your technical work, delivery, risk management, and ability to catch problems all depend on people raising their hands when something's wrong, whatever culture they grew up in. Some will still find it easier to speak through anonymous feedback channels, and those are worth having.
Leaders who get this right treat trust as a design problem. They ask what structures, practices, and norms they need so that people from different cultures actually feel safe speaking up, and they spend less time worrying about how trustworthy they seem.
Building trust across distributed, multicultural teams takes more than good intentions. It takes design. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, trust, and how teams actually perform. Subscribe here.