How to Fight Isolation on Remote Teams

Tomás shipped for a year without a single bad month. Clean pull requests, careful reviews, never missed a date. His manager would have named him one of the most reliable people on the team. Then he resigned, and in the exit conversation he said the thing that made the room go quiet: "I never really felt like I was part of anything. I was a name that closed tickets."

His manager was blindsided, and I understand why. Every signal she had access to said Tomás was fine. The work was fine. What she couldn't see was that he'd spent twelve months eating lunch alone in Lisbon while his team joked in a channel he'd stopped opening, and that the distance between "does good work" and "feels like they belong here" had grown wide enough for him to walk out of.

That gap is the quiet killer on distributed teams, and almost nobody manages it, because it doesn't show up anywhere you're looking.

The connection you used to get for free

Think about how you actually became friends with people at an office. You didn't schedule it. You stood at the coffee machine and someone made a joke. You walked to lunch and found out a coworker also had a toddler who wouldn't sleep. You lingered after a meeting and complained about the same thing. None of that was on a calendar. It was the byproduct of being in the same room, and it built the trust that made the actual work go smoother later.

Remote deletes all of it. Not on purpose, and not with any drama. It just quietly removes every unscheduled moment where two people used to bump into each other, and it turns out those moments were doing enormous load-bearing work. What's left is the work itself: tickets, docs, calls with an agenda. Everything that has a reason to exist survives, and everything that didn't, the small human stuff, silently doesn't.

This is the part teams underestimate when they go remote. They plan the work carefully. They set up the async-first communication and the handoffs and the standups. And they assume the friendship layer will just happen the way it always did, not noticing that the thing that made it happen, physical proximity, is exactly what they removed.

You can't see it until someone's gone

The reason isolation goes unmanaged is that it's nearly invisible from the outside.

A person who feels disconnected still logs in. Still closes tickets. Still says "sounds good" in the thread. Their output looks identical to a person who feels deeply part of the team, right up until the day it doesn't, and by then they've usually already decided to leave. There's no dashboard for belonging. No status field that reads "slowly drifting to the edge of the team." Managers track velocity and shipped features because those are legible, and they miss the thing that actually predicts whether someone stays, because it isn't.

It's worse for the person furthest from everyone else. The teammate nine hours off, the solo outlier a wide hiring map can strand, doesn't just miss the meeting. They miss the fifteen minutes of banter before the meeting and the two people who kept the call open afterward to keep chatting. Their day is the pure-work skeleton of the job with none of the connective tissue, and the effect compounds. Every week they feel a little more like a contractor and a little less like a colleague, and nobody notices, because from the outside they're still delivering.

Forced fun is not the answer

Here's where most teams go wrong once they finally do notice. They schedule connection. A mandatory Friday video happy hour. A recurring icebreaker where everyone shares a fun fact. A virtual escape room the whole company has to attend.

I want to be blunt: this usually makes things worse, and on a distributed team it's often actively cruel by accident. Picture that 5pm Friday happy hour set in San Francisco time. It's 1am in London, 2am in Berlin, 5:30am the next day in Bangalore. So the "team-building" event is comfortable for the people already at the center of the team and impossible for exactly the people most at risk of feeling like outsiders. You've built a party that structurally excludes the lonely, then labeled it inclusion.

And even for the people who can attend, forced socializing rarely produces the thing it's aiming at. Real connection is voluntary and a little bit sideways. It comes from a shared joke or a shared frustration, not from being told it's 4:45 and time to have fun on camera for twenty minutes. Mandatory fun has the exact texture of the thing it's imitating, minus the part that made it work, which was that nobody made you do it. People can feel the difference, and they resent the calendar hold.

Design connection into the work instead

The better approach is to stop treating connection as a separate event and build small, low-pressure, timezone-fair openings into the flow of normal work, so it can happen the way it used to: on the side, whenever, no performance required.

Start with the channel where non-work lives. A #random or watercooler space isn't a nice-to-have, it's the closest async replacement for the coffee machine, and it only works if the team's actual humans post in it, leaders included. When someone drops a photo of the trail they hiked or the dog that's ruining their standups, other people reply on their own time, from their own timezone, and a thread of nothing-in-particular becomes the place two people discover they both climb or both hate cilantro. It's async by nature, so the person in Bangalore joins the same conversation as the person in Denver, just six hours later, and neither had to lose sleep for it.

Celebrate the work in the open, too. When someone ships something good, say so in a shared channel rather than a private DM. Public, specific appreciation does double duty: the person feels seen, and everyone else gets a window into what their teammates are actually doing all day, which is one of the things proximity used to provide for free. A quiet team where all praise happens in private is a team where nobody feels part of anything bigger than their own task list, which is more or less what happened to Tomás.

Pairing helps more than any party. Put two people on a problem together for a few hours, even async, and they build the kind of low-stakes working relationship that no icebreaker manufactures. Rotate who pairs with whom so the connections form a web instead of a few cliques. This is also how a new hire stops feeling like an outsider, which is why good remote onboarding leans so hard on a buddy and real first work rather than a stack of docs.

The manager's actual job here

Someone has to own this, and it can't be "the team," because work that belongs to everyone belongs to nobody. On most teams it's the manager, and the highest-leverage tool they already have is the recurring one-on-one.

Use part of it to ask about connection, not just delivery. Not a survey question, an actual one: who have you talked to this week that wasn't about a ticket? Do you feel like you know the people you work with? The answers are the closest thing to a belonging dashboard you'll get, and they surface the drift while you can still do something about it, months before it turns into a resignation you didn't see coming.

If you do run live social events, and some are worth running, rotate the times the way you'd rotate a standup nobody wants to attend at 6am, so the cost of being awake at an odd hour gets shared instead of always landing on the same person. Better yet, keep the default connection async and reserve the rare synchronous hang for something people genuinely want to show up for.

None of this is expensive. It's a channel people actually use, praise said out loud, work shared instead of siloed, and a manager who asks the question nobody thinks to ask. The teams that keep people aren't the ones with the most elaborate virtual events. They're the ones where a quiet engineer in Lisbon never gets the chance to decide he's just a name that closes tickets, because a dozen small things all week kept reminding him he wasn't.

Keep Your Team on the Same Clock

Connection is harder when half your social channel is doing timezone math in their head to figure out if they can join the call. Timely converts every time mention in Slack to each reader's own timezone automatically, so "hopping on at 3pm if anyone wants to hang" reads correctly for everyone, and the person furthest away doesn't have to opt out just to avoid the arithmetic.

Add Timely to Slack — Free · See how it works