The first fully distributed team I led came together quickly, out of necessity rather than design. The organization had made a strategic decision to hire the best available people for roles regardless of location, and within eighteen months I was leading a team of seven people across five cities and two time zones. The initial period was productive in the specific sense that work got done — deliverables were completed, meetings happened, projects moved forward. What I noticed gradually, and then couldn't stop noticing, was how much slower the team was at navigating ambiguity, resolving disagreements, and developing the shared judgment that makes a team more than a collection of individuals doing related work.
The gap became clearest when I compared our team's performance with a similar team in the organization that was largely co-located. Their deliberations were faster and produced better outcomes. Their disagreements were resolved more quickly and with less residue. Their decisions reflected a shared understanding of each other's perspectives and capabilities that ours didn't, because they'd developed that understanding through thousands of small interactions — hallway conversations, lunch overlap, incidental contact — that our distributed team simply didn't have. The co-located team's cohesion wasn't a product of any particular team-building investment; it was the accumulated residue of daily proximity. We had to build deliberately what they'd built accidentally.
That experience taught me the most important principle of building cohesion in distributed teams: what physical proximity produces naturally in co-located teams must be produced deliberately in remote ones. Not through simulation of in-person experiences — virtual happy hours and digital watercoolers rarely produce the cohesion they're intended to — but through specific structural practices that address what proximity actually does for team cohesion, and that do those things in ways that work for distributed teams.
What physical proximity actually does
Physical proximity in co-located teams produces several specific conditions that contribute to cohesion, each of which must be deliberately engineered in distributed teams.
Incidental information flow. Co-located teams absorb enormous amounts of information through proximity — the overheard conversation that provides context on a colleague's challenge, the visible signs of someone's stress that prompt a check-in, the hallway exchange that surfaces a problem before it reaches the meeting agenda. Distributed teams don't have this incidental information flow, which means problems surface later, misunderstandings persist longer, and team members develop less accurate models of each other's situations. The structural substitute is more explicit communication about what's happening, not just formally but informally — practices that create the information sharing that incidental contact would otherwise produce.
Rapid feedback loops. Co-located teams can resolve small misalignments quickly because the cost of a brief exchange is low. In distributed teams, the friction of asynchronous communication and the time-zone overhead of scheduling synchronous time raises the cost of brief exchanges significantly, which means small misalignments that would have been resolved in a two-minute hallway conversation instead persist until the next scheduled interaction. The structural substitute is deliberate investment in low-friction communication channels — explicit norms about response time, clear guidance about what warrants synchronous versus asynchronous resolution, and the cultural permission to use quick, informal communication rather than waiting for structured meetings.
Shared context. People who share physical space develop shared context about the work environment — the organizational dynamics, the current pressures, the mood of the team — through continuous low-level observation. Distributed teams must build shared context deliberately through explicit communication practices that would be redundant in a co-located setting. The leader's responsibility here is to be significantly more explicit about context than a co-located leader needs to be: sharing the reasoning behind decisions, providing visibility into organizational dynamics that affect the team's work, and creating forums for the team to develop shared understanding of their environment.
What actually builds cohesion in distributed teams
The practices that build genuine cohesion in distributed teams are not simulations of in-person experiences — they're practices designed specifically for the constraints and affordances of distributed work.
Asynchronous communication discipline. The single highest-leverage investment a distributed team can make is developing genuine excellence at asynchronous written communication. This means more explicit framing than people are used to — documenting the reasoning behind decisions rather than just the decisions, providing context that a co-located colleague would have through proximity, and writing in ways that anticipate the questions a reader who wasn't in the conversation might have. Teams that develop this discipline find that their asynchronous communication produces better understanding than most organizations' synchronous communication, because the explicitness required for remote work forces a clarity that proximity often makes unnecessary. The transparency practice that builds organizational trust has its distributed-team analog in the explicitness of remote communication.
Deliberate relationship investment. The relationships that make distributed teams cohesive are built through intentional investment, not through incidental contact. This means specific practices for one-on-one connection that aren't primarily about work — conversations that give people genuine visibility into each other as people rather than as role-occupants. For distributed teams, this investment has to happen in structured ways because the incidental opportunities aren't there: regular one-on-ones with agenda time explicitly for non-work topics, periodic virtual sessions where the explicit purpose is connection rather than output, and in-person gatherings invested intentionally in the relationship-building that distributed work makes difficult.
Clear decision rights and norms. Distributed teams suffer disproportionately from ambiguity about who makes which decisions, because the informal negotiation that resolves that ambiguity in co-located teams requires communication overhead that distributed teams often don't invest in. Explicit, documented decision rights — who can decide what, when escalation is needed, what the default is when agreement can't be reached — reduce the overhead significantly and prevent the misalignments that accumulate when decision authority is unclear.
In-person time: using it well
For most distributed teams, periodic in-person gatherings are worth the cost — not primarily for the work that gets done in them, but for the relationship infrastructure they build that makes distributed work more effective in the months between them. The mistake that reduces the value of in-person gatherings is filling them primarily with formal work: presentations, status updates, decision meetings that could have happened remotely. These are not what in-person time is uniquely good at.
What in-person time is uniquely good at is building the relationship quality that enables productive disagreement, honest communication, and the kind of trust that allows difficult conversations to happen cleanly. The in-person gathering that invests its time in shared experiences, genuine conversation about work and non-work topics, and the deliberate building of personal relationships among team members produces a return in remote team cohesion that the agenda-dense work session doesn't. The distributed team leader who plans in-person gatherings with relationship investment as the primary objective is making a different and better investment than the leader who treats in-person time as a premium slot for formal work.
The related investment is making the in-person time include the people who most need it — the team members who joined remotely and have never had the kind of in-person contact that builds the deepest working relationships. Distributed teams that have a cohesive in-person core and a more peripheral remote membership will reproduce the cohesion gap between co-located and remote team members within their own structure. Intentionally using in-person gatherings to build relationships across the team — particularly involving remote members in the relationship-building that produces the shared context they've been missing — is one of the most specific and valuable investments available to the distributed team leader.
The leader's specific role
The distributed team leader has to do something that their co-located counterpart doesn't: actively create the conditions that proximity would create automatically. This is more work, and it's work that requires a different kind of attention — noticing the signals that something is off that would be visible in a co-located team and invisible in a distributed one, and investing in the relationship infrastructure that makes difficult conversations possible when proximity isn't doing that work.
The most common mistake distributed team leaders make is treating remote work as equivalent to co-located work with a video call substituted for an in-person meeting. The video call is better than nothing; it is not equivalent to physical presence for the purposes of relationship-building, incidental information sharing, or conflict resolution. Distributed team leadership requires genuinely different practices, more explicit communication, and more intentional investment in what proximity would otherwise produce for free. The leaders who build genuinely cohesive distributed teams are the ones who have accepted that investment as a non-negotiable feature of the role, not an optional enhancement. The same five foundations of high-performing teams apply — the structural work to build them is more deliberate and more explicit in distributed contexts.