Two teams, opposite problems
I learned to lead at a distance the hard way, managing development teams across three continents. I expected cultural differences between the teams to be our biggest challenge. I didn't expect them to change how I thought about leadership.
My team in Southeast Asia came from a culture where hierarchy and respect for authority were fundamental values. At first I read their quiet agreement with my suggestions as alignment, but our execution kept falling short. They weren't sharing ideas, pitching alternatives, or taking ownership of the development process. They did exactly what I asked and nothing more. They didn't realize they had 'permission' to push back on my ideas or suggest improvements.
Halfway around the world, I had a team from an extremely egalitarian culture where questioning authority was expected. Every suggestion I made met immediate pushback and heated debate. I got defensive and frustrated, and I decided they were trying to undermine my leadership.
I was wrong about both teams. Each of them was trying to help me succeed, and they showed it in completely different ways. The quiet team's silence meant there was a problem I was missing. The argumentative team's debates were engagement: people thinking hard about how my ideas would hold up once someone had to build them.
So I had to learn to read virtual body language, build relationships across cultural contexts, and set up structured ways for different communication styles to contribute. Within six months, our distributed team was generating more innovative solutions and making better decisions than any co-located team I had ever managed.
What I built
Remote leadership turned out to be no harder than in-person leadership. It just had to be more deliberate, and the systems I built for my distributed teams ended up better than what most co-located teams ever develop.
Psychological safety had to be built differently for each team. My Southeast Asian team needed explicit permission to disagree. I started asking individuals directly for alternative approaches and praising pushback when it happened, until they trusted that dissent was welcome. My European team needed structured ways to channel their debates, so that passionate disagreement ended in a decision and not an endless loop. I ran retrospectives where people shared mistakes alongside wins, and I set explicit norms for making sure everyone's voice got heard. The norms differed by team because the communication styles were so different.
With teams spread across continents, I couldn't make quick calls in a hallway. I created decision templates that recorded what was decided along with the context, the alternatives we considered, and the reasoning. That "consultation trail" earned its keep. My Southeast Asian team could review the reasoning and push back in writing on their own time, which was more comfortable for them than challenging me live. We also learned to use the time zones: one team would analyze user feedback overnight so the next team started its day with insights ready to act on.
Autonomy needed different boundaries for each team. My European team did best with broad autonomy and few check-ins, because they wanted room to debate and decide. My Southeast Asian team at first needed tighter guardrails and more frequent calibration, not because they were less capable, but because their professional culture sent different signals about what "ownership" looked like. I wrote down which decisions each team could make on its own, which required consultation, and which needed my approval, and I updated those boundaries as people grew. I used my one-on-ones to find out whether people felt supported and had enough room to decide. Nobody's performance was on the table in those meetings.
What an office lets you skip
Distance forced me to build leadership habits I never would have developed in a co-located environment. I had to make implicit expectations explicit, write down reasoning that would normally live in hallway conversations, and design different approaches for different people when I would have assumed one style worked for everyone.
Those are just good leadership practices. In an office you can get away without most of them, because someone fills the gap in a hallway or over lunch. With teams on three continents nobody fills the gap, so you either build the practice or the work stalls.