When Bruno and I started building the PipelineRoad team, we hired for talent first and location second. This is the standard remote-company line, and it’s true as far as it goes. But what nobody told us — and what I wish someone had — is that hiring across cultures doesn’t just mean managing across time zones. It means managing across entirely different frameworks for what trust looks like, how disagreement works, and what professionalism means.
I’ve traveled to more than forty countries, and that experience gave me a head start in recognizing cultural difference. But recognizing difference as a traveler and managing it as a leader are fundamentally different exercises. When you’re traveling, cultural friction is charming. When you’re trying to ship a deliverable on a Thursday deadline with a team spanning three continents, it’s a leadership challenge that requires real thought.
The Trust Asymmetry
The first thing I learned is that trust is not built the same way everywhere.
In some cultures, trust starts with competence. You demonstrate that you know what you’re doing, that your work is excellent, that you deliver on commitments. The relationship follows from the respect earned through performance. This is roughly how trust works in Northern European and Anglo-American professional contexts, and it was my default assumption because it’s the water I grew up in.
In other cultures, trust starts with relationship. You share a meal. You ask about someone’s family. You invest time in knowing them as a person before you expect them to be vulnerable or direct with you as a colleague. The competence is assumed or evaluated separately — it’s not the foundation of the relationship.
These two models are not in conflict, but they operate on different timelines and require different behaviors from a leader. If you manage someone from a relationship-first culture and you skip straight to performance feedback without investing in personal connection, you haven’t been efficient — you’ve been cold. And if you manage someone from a competence-first culture and you spend thirty minutes on personal conversation before getting to the work, you haven’t been warm — you’ve been unfocused.
Directness and Its Discontents
The second cultural variable that caught me off guard was directness. I’m a fairly direct communicator. If something isn’t working, I say so. If I disagree, I disagree openly. I assumed this was a universal virtue — who doesn’t want honesty?
What I discovered is that directness, in many cultures, is not a virtue but a violation. It signals disrespect, aggression, or a lack of social intelligence. In these contexts, disagreement is communicated indirectly — through questions, through silence, through what is not said rather than what is. A “yes” might mean “I hear you” rather than “I agree.” A lack of pushback might signal deep discomfort rather than alignment.
This was a real problem early on. I’d leave team meetings feeling like everyone was aligned, only to discover days later that half the team had concerns they hadn’t raised. I initially interpreted this as a confidence issue and tried to “create space” for people to speak up. That’s the American management playbook: encourage open dialogue, make it psychologically safe, and people will share.
But for some team members, the issue wasn’t psychological safety in the Western sense. It was cultural. Publicly contradicting a founder in a meeting is simply not done in some professional traditions, regardless of how many times you say “I want to hear pushback.” The format of the conversation itself was the barrier.
The solution was channel diversification. I started collecting input through multiple formats — written reflections before meetings, anonymous feedback forms, one-on-one conversations where the dynamic was different from a group setting. The same person who would say nothing in a team call might send a thoughtful, critical three-paragraph message in a DM. The insight was there. I just had to create the right container for it.
Time, Formality, and the Small Stuff
There are a dozen smaller cultural variables that, in aggregate, define the texture of a working relationship.
Attitudes toward deadlines vary. In some cultures, a deadline is a commitment — missing it is a professional failure. In others, it’s an aspiration, and flexibility is expected when circumstances change. Neither is wrong, but if these expectations aren’t explicitly aligned, resentment builds on both sides.
Formality varies. Some team members address me by first name from day one. Others default to a formal distance that takes months to relax. I used to try to accelerate that informality, thinking it was a sign of trust. I’ve since learned to let people set their own pace. Forcing casualness on someone who’s culturally wired for formality doesn’t build rapport — it creates discomfort.
Even meeting behavior varies. Who speaks first. How long someone waits before responding. Whether it’s acceptable to interrupt. Whether silence means contemplation or confusion. I’ve been in meetings where a team member’s three-second pause before answering was interpreted by another team member as hesitation or lack of confidence, when in reality it was simply how they processed — thoughtfully, before speaking.
What I’ve Changed
Managing across cultures has made me a better leader, but it’s required real adaptation. Here’s what I do differently now compared to two years ago.
I ask about preferences explicitly. During onboarding, I now ask new team members directly: How do you prefer to receive feedback? Are you comfortable disagreeing with me in group settings, or would you rather do that privately? When I set a deadline, how do you interpret that? These conversations feel slightly awkward, but they prevent months of miscommunication.
I default to written communication for important decisions. Written formats give people time to compose their thoughts, to disagree carefully, to translate if needed. The real-time meeting is great for energy and alignment, but the written follow-up is where accuracy lives.
I check my assumptions constantly. When someone is quiet in a meeting, I no longer assume they have nothing to say. When someone agrees quickly, I no longer assume they’re fully aligned. When someone misses a nuance, I consider whether the issue is language, culture, or genuine misunderstanding — and I respond accordingly.
I invest in the relationship before I need it. This is the simplest and most important change. Before I need to give someone hard feedback, before there’s a conflict to navigate, before a deadline is at risk — I invest time in knowing them. Their background, their motivations, what they care about outside of work. This investment pays dividends when the difficult moments arrive, because the foundation is already there.
The Reward
A culturally diverse remote team is harder to manage than a homogeneous local one. I won’t pretend otherwise. The communication overhead is real. The potential for misunderstanding is higher. The leadership energy required is greater.
But the output is also richer. Different cultural perspectives produce different solutions. Someone shaped by one professional tradition will see angles that someone from another tradition would miss entirely. The creative tension that comes from genuine diversity — not performative diversity, but the real kind, with real friction — is a competitive advantage that most companies talk about but few actually experience.
Building trust across cultures is slower. It requires more patience, more humility, more willingness to be wrong about your assumptions. But the trust you build is deeper for having been built deliberately, across real distance. And a team that trusts each other across cultural lines can do things that a team of similar people, no matter how talented, simply cannot.