Most engineering orgs will tell you their remote tooling works. Standups happen. Documentation gets written. Decisions get made and recorded somewhere searchable. And yet trust between teams that rarely interact keeps eroding anyway, in a way nobody can quite trace back to a specific broken process, because the process is not what broke.

A thought leader who examines disconnection for a living has a theory for why that gap is so hard to name. Edward Garcia spent years applying it to cities and public health systems before turning it toward distributed teams specifically. His starting point is that an office was never only a workspace. It doubled as something closer to plumbing: mostly invisible, quietly responsible for a lot more than anyone gave it credit for.

Garcia's diagnosis is specific rather than nostalgic. Companies that went remote did the obvious part of the job well. Meetings moved to video calls. Memos became shared documents. Hallway conversations became Slack threads. What never got rebuilt, in his view, is the layer sitting underneath all of that: the unplanned interaction that used to happen without anyone scheduling it, a new hire absorbing how senior engineers actually work by watching them, someone overhearing a conversation that turns out to be relevant to a problem they are stuck on.

The practical effect, in his read, is that distributed teams get very good at one kind of connection and steadily worse at another. People who already know they need to talk to each other can do so instantly, from anywhere. People who do not yet know they have a reason to talk almost never find that out by accident anymore, because accident was doing more work than anyone realized.

Independent research backs the pattern. A 2022 study in Nature Human Behaviour, based on six months of data from more than 61,000 Microsoft employees, found that firm-wide remote work caused collaboration networks to become more static and siloed, with fewer bridges between parts of the organization that did not already work closely together, alongside a broader shift from synchronous toward asynchronous communication.

Garcia heads off the obvious response before it lands. Ordering people back into an office does not fix this on its own, because sitting in the same building was never actually the mechanism. A team can be fully in person five days a week and still barely know each other outside their immediate group. What mattered was never the room. It was the conditions the room happened to create without anyone designing them on purpose.

He calls the discipline of recreating those conditions deliberately Social Connection Architecture, a framework he developed through his work co-founding the Global Initiative on Loneliness and Connection. Applied to a distributed team, the idea is to stop asking how to make remote work feel like an office and start asking what specific relational functions the office used to perform, then design deliberately for those functions instead.

In practice, Garcia's prescription is smaller than most remote culture initiatives, and less frequent than people expect. Not a retreat. Not a virtual happy hour, which he considers an occasional event rather than something that reliably builds trust over time. His preferred fix is short, repeated conversations between people who have no immediate work reason to talk, engineers from different teams paired for twenty minutes every few weeks, with nothing required to come out of it. The point is not the conversation itself. It is getting close to what used to happen by running into the same person often enough to actually know them.

“If every conversation has an agenda, deliverable, facilitator, and performance objective, you have simply created another meeting,” Garcia said. Strip the productivity requirement away, in his framing, or the exercise stops functioning as the thing it was meant to rebuild.

He is equally specific about what shared time in person should be used for once a team does travel to be together. Two days of conference room presentations people could have watched from their desks wastes the one resource distributed teams cannot get back easily. Garcia argues that scarce in-person time works better spent on mentoring, difficult conversations, and the kind of problem solving that genuinely benefits from being in a room, rather than the parts of work that already function fine on a screen.

“The lesson from remote work is not that connection requires an office,” Garcia said. “It is that connection requires infrastructure.” The office supplied that infrastructure so quietly that almost nobody registered it as infrastructure while it was still there. Its absence has been just as easy to miss, which is exactly why it keeps costing companies more than most of them have noticed.

This story was distributed as a release by Jon Stojan under HackerNoon’s Business Blogging Program.