Login
Back to Blog
Remote WorkDistributed TeamsHybrid WorkManagement

When Half Your Team Shares an Office

Rajat KapoorNovember 10, 20268 min read

The engineering team made a real decision on a Tuesday afternoon, and three of the people it affected weren't there. Four of them were in the Denver office, gathered around someone's monitor, and by the time the conversation wound down they had changed the shape of the next release. Nobody set out to leave anyone off. It just happened the way things happen in a room. Someone asked a question out loud, someone answered, a third person pushed back, and twenty minutes later there was an answer that nobody had written down because nobody needed to. The three remote engineers found out the next morning, from a one-line Slack message that assumed a context they didn't have. They spent that day half a step behind, asking questions the room had already closed.

That is the hybrid team's signature failure, and it is quieter and more corrosive than anything a fully remote team ever deals with. The remote people aren't being ignored. They're just downstream of a conversation they couldn't join, finding out what was decided after it was decided, and slowly learning that the real work happens in a room they're not in.

The hardest setup is the half-and-half one

Most leaders get this backwards. Fully remote is not the difficult configuration. The partially remote one is.

When everybody is remote, the playing field is level by force. Nobody has a hallway, so nobody can rely on one. Decisions have to be written down because there is no other way to make them. The team builds the habits of distributed work out of pure necessity, because the alternative is that nothing gets communicated at all.

A hybrid team gets none of that pressure. The office people have a working, comfortable, zero-effort way to coordinate: they talk. So they talk, and the written channel that the remote people live in becomes a secondary feed, a place where decisions get announced rather than made. You end up with two teams wearing one name. There is the team in the room, which moves fast and shares context by breathing the same air, and there is the team on the other end of a Slack thread, which gets the residue. The gap between them isn't malice. It's physics. A conversation is just faster and richer than typing, and water flows downhill.

The office is a context machine nobody can see

Spend a day in an office after months of remote work and you notice how much information moves through it that never touches a keyboard. You overhear that the client call went badly. You catch the tail end of a debate about the database and absorb the conclusion without ever asking. You see someone's face fall when a number comes in. None of it is written anywhere, none of it was meant as communication, and all of it is building a shared picture in everyone who happens to be present.

For the people in the room, that picture is free. For everyone else, the room is a sealed box. The remote engineer isn't missing one decision. They're missing the thousand small updates that made the decision obvious to everyone who was there, so when the one-line summary arrives it reads as arbitrary, because the reasoning stayed in the air of the office and never made it onto the screen.

On a lot of hybrid teams the office cluster also shares a timezone, usually headquarters' timezone, which means the in-room people hold two advantages at once. They share the room and they share the clock. The remote teammate nine hours away is on the outside of both, learning what the office settled on while it was still their night, catching up on a conversation and a workday that both ended before theirs began. The two gaps stack, and the person on the wrong side of both quietly stops expecting to be part of how things get decided.

Run the office by remote rules, not the other way around

The common instinct is to fix this by asking the remote people to try harder. Speak up more in meetings. Check Slack more often. Don't be shy about asking what you missed. This never works, and it is unfair besides, because it puts the cost of the broken setup on the people the setup already disadvantages.

The fix runs the other direction. You make the office people behave as though they were remote. That sounds strange until you try it, and then it is obvious.

Take the meeting from your own laptop even when the person you're meeting is ten feet away, so the remote attendee is in a grid of equal squares instead of a tiny window watching a conference room where they can't tell who just spoke. When a hallway conversation turns into a real decision, it does not count until it lives in writing where the sleeping half of the team can read it in the morning. That is just making the decision the way a distributed team already has to, with a short written proposal and a named owner, rather than letting the room settle it and calling that settled. The reflex to grab someone at their desk for a quick answer is the exact reflex you have to catch, because every time you resolve something in person that the whole team needed, you have widened the gap by one more thing the remote people will find out late.

None of this means the office is forbidden. People who like working near each other should get to. It means the office stops being the place where the actual work happens and becomes just a nice place some people work from, with no special access to context or decisions attached to the chair.

Write it down, or it didn't happen to the people who weren't there

The single habit that saves a hybrid team is almost boringly simple: the default home of a decision, a plan, or an answer is written and shared, not spoken and remembered. Put the durable version in a doc the moment the conversation ends, while it is fresh, so the person who was asleep can self-serve the reasoning instead of pinging someone to re-explain it a sleep cycle later. An office team can get away with a verbal culture because everyone was there. The moment one person wasn't, the verbal culture is actively excluding them, and on a hybrid team somebody is always the person who wasn't there.

This is the same discipline that makes async-first communication work on a fully distributed team. The difference is that a hybrid team has to adopt it on purpose, against the gravity of a room that makes the lazy path feel fine. If writing things down feels like unnecessary overhead, that is precisely the feeling of the office people enjoying a shortcut the remote people can't use.

Watch where the visible work ends up

The cost of a two-tier team isn't only daily friction. It compounds into careers. The person in the room gets handed the high-stakes project because they were standing there when it came up. They get the unplanned face time with the visiting executive, the casual lunch where a reputation gets built, the hundred small moments of being seen. Months later, when it is time to decide who is ready for more, leadership has a vivid picture of the office people and a thin one of everyone else, and they mistake the vividness for merit. This is how proximity quietly tilts promotions, and a hybrid office pours fuel on it, because the proximity is real and it clusters in one physical place.

So pay attention to where the good work lands and who gets the visible slots. If the stretch assignments and the demos and the exec exposure keep going to whoever shares the building, the problem isn't a run of coincidences. It's the setup doing what the setup does. Fixing it means deliberately routing opportunity to the people who aren't in the room, and judging everyone by what they actually produce rather than how often you see their face, which is the only fair measure once part of your team is somewhere you can't watch them.

The hybrid team can absolutely work. It just won't work by accident, because left alone it reverts to the room. You have to decide, on purpose and repeatedly, that the office is a place to sit and not a tier to belong to.


Related Reading


Let Timely Handle the Clock Math

When part of your team shares an office and the rest are scattered across timezones, every "let's sync after lunch" means one thing to the room and something else to the person half a world away. When someone writes "demo at 2pm" or "standup moved to 9:30," Timely reads each person's Slack timezone and shows that moment in their own local clock, so the remote half never has to do the conversion the office never notices it's asking for.

Add Timely to Slack — Free  ·  See how it works