A distributed team is not a co-located team with worse tooling. It’s a different thing, and treating it like the first version is how you end up with a team that technically works together but never actually clicks.

I’ve led teams split across the US and Europe, and teams with one person in a timezone eight hours off from everyone else. The patterns that show up are pretty consistent. Here’s what I’ve found that matters.

What I mean by distributed

If your people don’t sit in the same room, you’re distributed. It doesn’t matter if they’re across the city or across an ocean. The moment someone is dialing in, the meeting is a remote meeting, and the team is a remote team. Pretending otherwise is the first mistake.

Get the boring stuff right first

Most of the problems I see on distributed teams aren’t strategic. They’re that the audio is bad, the chat tool is a mess, and nobody knows where to find anything. Fix those first.

Chat

Slack is fine. Teams is fine. Pick one and commit. A few things that matter more than the tool:

• Get every team onto it. The moment two teams are on different platforms, the cross-team work falls apart.
• Write rules for @channel and @here and post them somewhere people can find them. Otherwise someone will eventually @channel a 4,000 person workspace to ask about the broken espresso machine.
• Tell your team to over-share context in writing. The person reading your message cannot lean over and ask what you meant. Write the sentence you’d have said in the hallway, then write the sentence after that.

Video

For most of the teams I’ve been on, the answer has been Zoom. Audio is consistently good, scheduling is painless, and the rest of the world has figured out how to use it. Google Meet is fine for ad hoc calls and external guests because there’s nothing to install. I’ve used Webex and would not pay for it again.

Hardware

This is where companies cheap out and regret it. Two things to spend on:

• A real headset for everyone working from home. Not earbuds. A headset with a boom mic. I’ve heard a lot of meetings ruined by someone’s laptop mic picking up the dishwasher.
• A decent conference mic for any room people will dial into. The Jabra Speak 510 has done well for me. It’s cheap relative to the time you save by not having to ask “can you say that again” every two minutes.

A few people on your team will also need to think about their room. Ticking clocks, a window onto a busy street, a hard wall behind the mic that bounces sound. None of it sounds like a problem until it’s amplified through a call.

Call hygiene

Mute when you’re not talking. Assume there will be a half-second delay and stop talking over people. If the audio is bad, say so out loud the moment you notice. The longer you let bad audio go, the more of the meeting is wasted.

Culture is not a side topic

The thing nobody warns you about when you start leading a global team is how often a totally benign exchange goes sideways because two people have different defaults for what “yes” means, or how disagreement is expressed, or how feedback is delivered.

The fastest way I know to get less dumb about this is to read The Culture Map by Erin Meyer. It gave me a vocabulary for things I’d been bumping into for years without being able to name them. After that, the work is paying attention and being willing to ask “hey, did that land the way I meant it?” more often than feels comfortable.

The trap to watch for is the “us vs them” framing. When something goes wrong across geographies, the easy story is that the other office dropped the ball. That story is almost never the whole picture, and even when it is, telling it that way makes the next handoff worse.

Get them in a room sometimes

I’ll say this plainly. Distributed teams that never meet in person plateau. Twice a year is the minimum I push for. New teams should meet face to face within the first few months if at all possible.

A good in-person week is some mix of:

• Working sessions on the hard problems that haven’t been moving
• Time with stakeholders the remote team rarely sees
• A customer visit if you can swing it
• Dinner, a long walk, a bad karaoke night, whatever it takes for people to remember they like each other

The work that gets done in those weeks is real, but the part that pays off for the next six months is the relationships. When two people have shared a meal, they ask harder questions and forgive smaller offenses over Slack.

If you can, go visit your teammates where they live and work. Seeing someone’s commute, their office, the coffee shop they like, changes how you read their messages forever.

The short version

• Fix the tools and the audio before you fix anything else
• Take cultural difference seriously and read The Culture Map
• Write more than you think you need to
• Get everyone in a room at least twice a year

None of this is novel. The hard part is doing it consistently when the team is busy and travel budgets are tight. The teams that hold the line on these basics are the ones I’ve watched outperform their co-located peers.