Connection on Remote and Hybrid Teams: When Proximity Isn't Doing the Work

The Conversation That Was Never Scheduled

In an office, a ten-minute conversation with a colleague may never have been arranged at all. You arrived early. Someone was refilling the kettle. A meeting finished four minutes under and two of you walked back the same way. Nothing important was supposed to happen, and usually nothing important did. But over months, those unplanned minutes were how coworkers stopped being job titles to each other.

When work becomes distributed, the work itself often continues perfectly well. The documents get written, the calls happen, the deadlines land. What quietly stops is the contact nobody ever decided to have. Building connection on a remote or hybrid team means creating opportunities for ordinary, low-pressure contact — without turning every interaction into a meeting, an event, or a scheduled social activity. That sentence contains the whole problem, because the obvious fix and the actual fix point in opposite directions.

This article is about what changes when coworkers no longer consistently share a place: which forms of connection disappear, which survive untouched, and which have to become deliberate. It is not about remote productivity, and it takes no position on where anyone should work.

What Actually Changes When Work Becomes Distributed

It helps to separate four things that get bundled together whenever distributed work is discussed.

Communication is the exchange of information — messages, calls, documents. Coordination is knowing who is doing what and when. Collaboration is producing something together. Connection is the relational familiarity underneath all three: knowing who someone is, being comfortable asking them something small, having a sense of how they are doing this week.

Distributed teams usually solve the first three, sometimes better than they did in an office. The fourth is the one that thins, and it thins in a way that is easy to miss because the other three look healthy. A team can exchange four hundred messages a day and still contain people who know almost nothing about each other. Volume of communication is not a measure of connection, and using it as one is the most common diagnostic error on remote teams.

What distance actually changes is the supply of opportunities. In a shared place, a certain amount of contact is produced by the environment: you pass people, you queue behind them, you overhear things. Remove the shared place, and every interaction has to be produced by a person deciding to produce it. That is the whole mechanism. It is not that remote workers are lonelier, or less social, or less committed — it is that a supply of unplanned encounters stopped arriving on its own.

The largest single study of this pattern examined anonymised communication data from 61,182 US employees at Microsoft during the first half of 2020, comparing people already working remotely before the pandemic with those newly sent home. Within that sample, collaboration networks became more static and more siloed: fewer new bridging connections formed between groups, existing strong ties intensified, and communication shifted toward asynchronous channels. It is worth being precise about what that does and does not show. It is one very large technology company, during an abrupt and involuntary transition, in an unusual global period. It observed collaboration structure — who talked to whom — not loneliness, belonging, wellbeing, or trust. It cannot be read as a verdict on remote work generally. What it does do, better than any anecdote, is confirm that the pattern people describe informally is real and measurable: contact concentrates around the people your work requires.

The Interactions We Rarely Notice Until They're Gone

Ask someone what they miss about the office and they rarely say the meetings. They say things that sound trivial written down.

The four minutes before a meeting starts, while people wait for the last person to join. The walk back afterwards, which is where the actual reaction to the meeting gets said. Making coffee at the same time as someone from a different team. Passing a desk and noticing that a colleague looks like they have had a bad morning. Eating near people you do not work with. Being interrupted by a question that was not worth a message. Overhearing a problem you happen to know the answer to.

These share three properties: nobody planned them, nobody had to justify them, and each one was individually forgettable. Their value was cumulative. This is close to what Sias and Cahill found when they interviewed coworkers about how their relationships had developed — proximity, shared work, and repeated unplanned contact kept recurring in people's accounts of how a colleague had gradually become someone they knew.

It is important not to romanticise this. Physical proximity never guaranteed connection, and the assumption that it did is why so many return-to-office arguments are unpersuasive. Bernstein and Turban's field studies used wearable sensors to track interaction before and after organisations moved to open, boundary-free offices, and observed face-to-face interaction falling substantially while electronic messaging rose. Put people in a room together with no privacy and no reason to talk, and many of them will put on headphones and message each other. Proximity is not a connection strategy; it is a set of conditions that sometimes produces contact.

Fayard and Weeks looked directly at those conditions, studying why the photocopier room in one organisation generated conversation while the identical facility in another generated none. What mattered was a combination of privacy, proximity, and — crucially — a legitimate reason to be standing there. People need somewhere to be where being there does not require an explanation.

That finding is the most useful thing in this entire article, because it means incidental contact was never really about buildings. It was about having a plausible reason to be somewhere, with a low chance of interruption cost, repeatedly. Those conditions can be recreated at a distance. What cannot be recreated is the part where it happened whether or not anyone thought about it. The wider question of why being near people is not the same as feeling connected to them belongs to The Difference Between Being Around People and Feeling Connected, which is worth reading alongside this one.

Strong Ties Aren't the Whole Workplace

When contact has to be initiated, people initiate it with the colleagues they need. This is entirely rational and it produces a specific casualty: the people you did not need.

Granovetter's 1973 argument about weak ties is the reference point here, though it needs handling honestly — it is a sociological paper about acquaintance networks and job information from half a century before anyone joined a video call, and it says nothing whatsoever about remote work. Its enduring contribution is conceptual: the acquaintances at the edge of your network, not your closest contacts, are the ones connecting you to information and people you would not otherwise reach. Close contacts mostly know what you already know.

Applied to a workplace, your weak ties are the people you are friendly with but do not work with: someone in another team whose name you know, the person you always ended up next to at lunch, the colleague who joined the same month as you. They are the ones who tell you that a project has changed direction, who suggest the person you should actually be asking, and who make an organisation feel like a place rather than a chart.

These are precisely the relationships that require no maintenance in a shared building and considerable maintenance without one. Nobody schedules a call with a weak tie. There is no agenda item for it. In the Microsoft data, this showed up as fewer bridging ties being added between otherwise separate groups — the network kept working, but it stopped reaching outward. A reasonable read is that distance does not damage your closest working relationships much at all. It removes the outer ring.

Descriptively, this matches what people report. Microsoft's Work Trend Index, published in March 2021 and combining a commissioned survey of 31,092 workers across 31 countries with aggregated product telemetry, found many respondents saying their relationships with people outside their immediate team had weakened while relationships within it had held or strengthened. That is self-reported survey data from a company selling collaboration software, and it should be read as description rather than evidence. Cited with those limits, it points in the same direction as the network data.

The practical implication is unusual and specific: if you have limited energy for connection at work, spending it on the people you already speak to daily is the least valuable option available. The outer ring is where distance actually bites.

Why Another Video Meeting Is Not the Answer

The instinctive response to lost informal contact is to schedule it. If people no longer bump into each other, put a recurring social call in the calendar. This fails often enough that it deserves examination, because the failure is not about execution.

A calendar invitation changes what an interaction is. The hallway conversation had no start time, no participant list, no duration, and no record that you were there. Convert it into a recurring thirty-minute video call and it acquires all five. Attendance becomes visible. Absence becomes a small piece of information about you. A conversation that cost nothing now costs half an hour that has to be justified against everything else in the day.

There is also a straightforward load problem. Video calls are effortful in a way that standing near someone is not. Bailenson's paper proposing causes of what people call Zoom fatigue is explicitly a theoretical argument rather than a finding — it suggests mechanisms such as prolonged close-up eye contact, the unnatural experience of watching yourself all day, reduced physical mobility, and the extra cognitive work of producing and interpreting nonverbal cues through a screen. Related work by Fauville and colleagues developed a validated scale for measuring videoconference fatigue, which is self-reported tiredness, not a diagnosis. Neither line of research says video calls are harmful. What they support is something narrower and sufficient: a video call is not a low-cost interaction, and treating it as the replacement for low-cost interactions puts the cost in exactly the wrong place.

Then there is performance. When a social interaction is scheduled and attended visibly, people manage how they appear in it. Cameras on, a suitable background, a prepared answer to "how was your weekend". This is not a failure of sincerity; it is what anyone does when observed. But it is the opposite of what made incidental contact valuable, which was that nothing was at stake and nobody was assessing anything.

The distinction that resolves this is between access and requirement. Connection needs opportunity. Opportunity does not have to mean mandatory synchronous attendance. A door that is open is not the same as a door you must walk through.

Create More Doors, Not More Obligations

Here is the design principle in a form you can use. It is a Fika Pause editorial framework — a checklist drawn from practice and from the conditions Fayard and Weeks identified, not a validated scientific model. An opening for contact on a distributed team works better when it is:

Visible. People must know it exists. Contact that depends on being told privately reaches only whoever is already connected, which reproduces the problem.

Available. There must be a specific way in — a time, a channel, a window. "You can always message me" is not an opening; it is a policy.

Optional. Genuinely, observably optional. If non-attendance is noticed, commented on, or tracked, it has become a meeting regardless of what it is called.

Repeated. Once is an event. The value is in recurrence, because familiarity accumulates and because a repeated opening does not need to be organised each time.

Low-pressure. No agenda, no preparation, no expectation of disclosure, no requirement to be interesting. Camera optional. Leaving early unremarkable.

Applied, these look like: an open half-hour where one person is simply available and others may drop in; a channel where people post ordinary things and nobody is expected to; deliberately staying on for five minutes at the end of an existing call when the topic is finished and nobody is rushing; a small recurring group of three rather than a whole-team event; a shared work window where people are on a call doing separate work in silence.

Notice what these have in common. None of them creates a new obligation. Each one adds a door rather than a corridor everyone must walk down. The temptation is to turn this into a list of remote team-building activities, and the list is not the point — a badly designed activity that meets all five conditions will beat a brilliantly designed one that fails on optional. Getting any of this to survive past the third week is a separate craft, and it is the subject of Workplace Rituals That Last.

Asynchronous Connection Counts

There is an unhelpful assumption running through most remote-connection advice: that real connection is synchronous, and messages are what you settle for. This is worth rejecting outright.

Warmth accumulates asynchronously through recognisable moves. Remembering something a colleague mentioned and referring to it later. Checking back a week after someone said they had a difficult thing coming up. Acknowledging a specific contribution by name where others can see it, rather than a generic thanks. Sharing context that someone did not strictly need but would want. Writing in a way that sounds like a person — a fragment of personality in a message costs nothing and does a surprising amount of work. Answering a question fully rather than minimally.

Asynchronous contact also has genuine advantages over a call. It does not require two calendars to align across time zones. It gives people time to consider what they want to say, which suits plenty of colleagues better than being put on the spot. It leaves a trace, so context does not evaporate. And it does not demand the sustained self-presentation that video does.

That distinction matters enough to state directly: asynchronous connection is not the same thing as constant availability. A green status dot is not a relationship. Nobody should have to remain permanently online to demonstrate that they are a connected member of a team, and any culture where responsiveness has quietly become the proof of commitment has confused surveillance with contact. Giving people time to respond is itself a form of respect, and it is one of the few things a distributed team can offer that an office cannot.

Remote Onboarding Is a Special Case

A new colleague joining a distributed team is missing two different things at once. The first is formal information — systems, processes, who does what — and most organisations have some plan for that. The second is ambient information, which almost nobody plans for because in an office it was absorbed rather than taught.

Ambient information is the answer to questions a new person often cannot yet articulate. Who do I ask when the question is too small for a meeting? Who actually knows how this works, as opposed to who owns it on the chart? Who talks to whom, and which two people should probably both be in this conversation? Is it acceptable to interrupt someone directly, or does that read as rude here? Which discussions are formal and which are not? How long is a normal response time? Is this team's flat tone friendly or is something wrong?

Cramton's research on dispersed teams describes exactly this territory as the mutual knowledge problem: information distributed unevenly without anyone noticing, silence being interpreted as meaning, and difficulty knowing what someone else's local situation actually is. For an established colleague, these are friction. For a new one, they are disorienting, because a new person has no baseline against which to judge whether anything is unusual.

The specifically remote fix is to make the ambient explicit. Say out loud who to ask about what, including the informal answer. Name the fact that short questions are welcome, because a new remote colleague will otherwise batch them into a weekly call. Introduce people to a handful of colleagues they will never work with. Explain the tone. Tell them what the silence means. Welcoming someone properly is a whole discipline of its own and belongs to Making People Feel Welcome at Work; what belongs here is only the part that distance makes harder — everything a person would otherwise have learned by being in the room.

Hybrid Work Creates a Different Problem

Hybrid is not remote work with occasional days in a building. It introduces a problem fully remote teams do not have: asymmetry.

On a fully remote team, everyone is in the same relationship to the information. Nobody heard anything in a corridor, so anything that matters has to be written somewhere. On a hybrid team, some conversations happen in a room and some do not, and the difference is invisible to the people who were in the room. A decision genuinely made over lunch gets referenced three days later as though everyone was there. A discussion that started before the call began continues into it, and the remote participants join something already in motion. The same three people happen to come in on Tuesdays and steadily become more familiar with each other than with anyone else. Informal context — someone's news, a shift in priorities, the reason a project stalled — travels along whoever happened to be present.

It is worth being careful here rather than sweeping. It does not follow that hybrid workers are automatically disadvantaged, and the evidence does not support blanket claims in either direction. Bloom, Han, and Liang ran a six-month randomised controlled trial with 1,612 graduate employees at a large Chinese travel company, comparing two work-from-home days a week against full office attendance; resignations fell and performance ratings were not damaged. One trial at one firm does not tell any other team how many days to be in an office, and it did not measure relationship quality at all. But it is enough to retire the assumption that hybrid arrangements are inherently costly, and to move the conversation to the thing that actually varies: how the team handles what happens in the room.

The principle worth holding onto is this: do not let physical presence become the hidden requirement for social or informational inclusion. Not a rule about days. A rule about what being in the building is allowed to buy you.

Make the In-Person Day Worth Travelling For

This section is editorial reasoning rather than a research claim, and it is offered as such.

If a team does gather physically, the useful question is not how often, but what physical presence uniquely makes possible. Two people travelling ninety minutes each way to sit in separate corners of an office on separate video calls have paid the full cost of proximity and received none of its benefit. That is not an argument against the office; it is an argument against treating attendance as the goal rather than the means.

The things proximity is genuinely good at are fairly specific. Unhurried conversation that nobody has to end at a fixed time. Eating together, which is the oldest connective technology anyone has. Messy collaborative work with a whiteboard and interruptions. Introductions between people who would otherwise never encounter each other. Welcoming someone new. Marking something — a finish, a departure, a milestone. Simply maintaining relationships that are otherwise sustained entirely through text.

The things proximity is bad at include most focused individual work, and every call where half the participants are elsewhere. A team that decides its in-person days are for the first list and protects them from the second gets a great deal more out of far fewer days. What makes a physical space feel like somewhere people want to be at all is a broader subject, covered in Creating Spaces Where People Feel Welcome.

What About Remote Fika?

A shared pause adapts across distance reasonably well, with conditions. It is worth saying plainly first: fika is not the solution to distributed work, and this article is not offering it as one. What fika actually is — a shared pause, usually with coffee and something to eat, where the point is the pause and the company — is defined elsewhere and not redefined here.

Adapted for distributed colleagues, it survives when it stays optional, when it does not acquire the shape of a status meeting, when nobody has to perform, when conversation needs no agenda, and when it is simple enough that it can happen again next week without organising. Those conditions are the same five from the framework above, which is not a coincidence — a pause is just an opening for contact with a cup in it.

It is also worth acknowledging that a fika may be solitary, and that this is not a lesser version. Two colleagues do not have to drink coffee simultaneously on camera for the practice to be worth anything. Stepping away from the desk properly, at roughly the time other people also step away, keeps the habit of pausing alive even when nobody joins. How to Practice Fika Every Day covers the personal version.

No claims are made here about what a remote pause produces. It does not manufacture trust, belonging, psychological safety, wellbeing, or output. What it can do is provide one repeated, low-cost opening in a week that otherwise contains none.

Connection Without Manager Permission

Almost everything in this article is available to someone with no authority whatsoever, which is the main reason it is worth reading.

Send the follow-up message — the one referring to something a colleague mentioned three weeks ago that you happened to remember. Invite one person rather than the department; an invitation to one costs nothing to accept or decline. Stay curious about people beyond their function, without interrogating them. Start a recurring voluntary pause with one or two colleagues and let it be small permanently. Make room before or after a conversation you were going to have anyway, rather than adding a new one. Deliberately include the colleague who is rarely physically present — copy them in, ask their view first, tell them what was said in the room. Pass on useful informal information rather than holding it, because information hoarding at a distance is invisible and therefore easy.

The skills underneath most of that — how to open, what to ask, when to stop — are covered properly in How to Talk to Coworkers and, for listening specifically, in How to Listen So People Feel Heard. None of it is different at a distance. Only the opportunity is.

What Managers Control That Coworkers Don't

Managers do not create relationships, and no manager can solve loneliness on a team. What they control is a set of conditions, and the conditions matter more than any initiative.

Calendar density, first: a week with no unscheduled time contains no room for anything informal, and no amount of encouragement compensates. Whether optional actually means optional, which is determined not by what is announced but by what happens to people who do not attend. Who receives information, and whether decisions made in a room reliably reach the people who were not in it. Whether informal participation quietly shapes who is regarded as committed — an especially sharp risk on hybrid teams. Whether relationship time is treated as legitimate work or as slack to be recovered. And whether anyone notices when a colleague has dropped out of view, which at a distance can happen for months without a single obvious sign.

That is a list of removals rather than a leadership programme, and the framing is deliberate. The case for why any of this deserves managerial attention is made in Why Connection at Work Matters, and how trust behaves specifically between colleagues is the subject of Belonging and Trust at Work.

When More Connection Isn't the Answer

A significant number of people are working remotely partly because they wanted fewer social interactions, and any article on this subject that ignores them is writing for half its readership.

Connection is not synonymous with interaction, and more of the second does not reliably produce the first. Some people are drained rather than energised by unstructured social contact, and that is a preference rather than a deficiency to be corrected — the caricature of the introvert who needs drawing out is both inaccurate and patronising. Some people are deliberately keeping work and personal life separate, which is a legitimate and healthy arrangement. Some are caring for a child or a parent between calls and have no discretionary minutes at all. Some are eleven hours away from most of the team and would have to give up an evening. Some come from a workplace culture where colleagues are simply not the people you confide in. Some are protecting the focused hours that remote work finally made possible.

None of those people need a connection intervention. What they need is for the team's social life to be arranged so that not participating carries no cost. That is the real test of whether an opening is optional.

People are not obligated to turn coworkers into friends. The goal of everything in this article is not maximum interaction; it is enough repeated opportunity that anyone who wants contact can find it, without anyone else being required to perform sociability to remain in good standing.

A Practical Remote and Hybrid Connection Check

This is a Fika Pause reflection exercise, not a diagnostic and not a survey. Read the questions honestly rather than scoring them.

• Who do I regularly interact with besides the people my work requires?
• If I had a small question, is there someone I could ask without it becoming a meeting?
• Are there any low-pressure opportunities for conversation on this team, or only calls?
• Do remote colleagues receive the same informal context as people who come in?
• Does "optional" actually feel optional here — and how would I know?
• When we do meet physically, do we use the time for things proximity is good at?
• Are there ways to connect asynchronously, or does everything require being live?
• Who on this team has quietly dropped out of my field of view in the last six months?

A team can answer badly on most of these and still be fine, if the people on it want little contact. The questions are useful only against what the people involved actually want.

Beginning This Week

One small thing, not a programme. Choose one colleague you already know but rarely encounter now — someone who used to be in your ordinary field of view and is not any more. Create one opening for contact that does not require a meeting. A message. A question about something they mentioned. A follow-up. An offer of a short optional pause at a time you were going to take a break anyway.

The aim is not to manufacture friendship. It is to restore one of the ordinary openings that distance quietly removed.

Where to Go Next

This article deliberately kept to one question: what changes about connection between colleagues when they do not share a place. The larger arguments live elsewhere in the library. Why connection at work is worth any of this effort is the series cornerstone, Why Connection at Work Matters. What repeated shared practices do for people in general is Shared Rituals and Human Connection, and the craft of making one survive is Workplace Rituals That Last. For the conversations themselves, How to Have Better Conversations is the capstone of the Conversation Skills series.

Later in this series, Honest Conversations at Work takes on feedback and disagreement where consequences are real, Psychological Safety at Work covers the team-level climate that decides what happens after someone speaks, and Building a More Human Workplace is the capstone that puts the pieces in order. The series page lists everything in reading order, and the Fika Pause Learning Path shows where this series sits in the wider library.

Knowledge Check

Frequently Asked Questions

The questions below are the ones most often asked about connection across distance. Where the full answer belongs to another guide — conversation skills, welcoming new colleagues, ritual design, or fika itself — the answer here stays short and points to the article that owns it.