Trust Across Cultures: Building Real Connection in Distributed Teams
The Silent Week That Revealed a Leadership Blind Spot
Giulia Scalaberni's remote team went completely silent for a week after she asked "any questions?" during onboarding. No one spoke up. No hands raised. Nothing.
The assumption many leaders make in that moment is straightforward: no questions means clarity achieved. The team understands. Move forward.
What actually happened was the opposite. Giulia's team included people from Austria, Italy, and India—each carrying different cultural frameworks about what it means to challenge authority, ask for help, or admit confusion in front of a group. In some of those cultures, raising your hand to say "I don't understand" in a full-team setting isn't a sign of engaged learning. It's a public admission of weakness.
This is where the gap between good intentions and actual leadership opens. A leader can genuinely want psychological safety and transparent communication, and still build systems that systematically silence the people who need to speak most.
What Erin Meyer's Culture Map Actually Tells You
Erin Meyer's research on cultural dimensions—published in "The Culture Map"—maps how different cultures approach trust, communication, feedback, and decision-making. But the framework only works if leaders use it to redesign their actual practices, not just nod along and keep doing what they've always done.
In high-context cultures (many parts of Europe, Asia, and Latin America), trust and psychological safety are built through relationship first, explicit permission later. A manager asking "any questions?" in an all-hands assumes a low-context norm: if you have something to say, you say it directly. But in a high-context environment, that question without prior relational groundwork doesn't create safety. It creates the appearance of openness while keeping people silent.
The Three-Question Workshop That Actually Worked
Giulia's fix was elegant and specific: she ran a three-question workshop during onboarding. No work talk allowed. The three questions were designed to let people introduce themselves as humans first: Where are you from? What do you love to do outside of work? What's something you've learned recently that surprised you?
This worked not because icebreakers are magic, but because it created 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 raise their hands when something's unclear—even in cultures where that goes against the grain.
The lesson is operative and testable: psychological safety in distributed, multicultural teams isn't something you declare. It's something you build through small, deliberate relational work before you ask for vulnerability.
The Decision Rule That Slows Down Urgency
Giulia runs her remote team across Europe and India with a principle she calls "everything urgent, nothing urgent really." The rule is simple: any decision that feels urgent gets held for 24 hours unless it's actually a safety issue.
This sounds like it could slow execution. In practice, it does the opposite. Most urgency is emotional urgency—it feels time-pressured because of how it lands, not because the clock is actually ticking. Slowing down decisions by a day separates the actual emergencies from the noise, and it gives distributed teams across time zones a chance to weigh in without being overridden by whoever's awake first.
For leaders managing across cultures, this rule also creates space for different communication styles to surface. Some cultures prefer asynchronous, written input. Some prefer real-time conversation. The 24-hour rule gives both time to show up.
Trust as an Operational Responsibility
Giulia's advice to senior leaders is grounded in operations, not sentiment: if your dishwasher doesn't show up, your whole restaurant has a bad night. The metaphor extends beyond the kitchen. Every person at every level—whether they're a senior engineer, a junior analyst, or the person managing infrastructure—is critical to the system working.
This means leaders can't treat trust and psychological safety as nice-to-have cultural values. They're operational inputs. A team where people don't feel safe to speak up about problems is a team where problems stay hidden until they break production or kill projects.
For distributed teams across cultures, this reframing is essential. You're not building trust to feel good. You're building it because your technical work, your delivery, your risk management, and your ability to catch problems all depend on people being willing to raise their hands when something's wrong—regardless of the culture they grew up in.
The leaders who get this right treat trust-building as a design problem, not a personality trait. They ask not "How do I seem more trustworthy?" but "What structures, practices, and norms do I need to build so that people from different cultures actually feel safe speaking up?"
Building trust across distributed, multicultural teams requires more than good intentions—it requires design. See how we work at Kestryl Edge.
Dan Korus, Kestryl Edge founder, publishes The Updraft, a weekly newsletter on leadership, emotional intelligence, and organizational performance. Subscribe here.