Half the Team Wasn't in the Room: When Proximity Bias in Hybrid Work Quietly Decides Who Gets Ahead
- William Rawe
- 48 minutes ago
- 4 min read
A decision gets made in a hallway on Tuesday. By Thursday, it is being referenced in a meeting as though everyone was there for it. Two people on the call have no idea what changed, and asking now would mean admitting they are three days behind on something that was never announced. They stay quiet. You read the silence as agreement.
This is the part of hybrid and distributed work that rarely shows up in an engagement survey. It is not that remote people feel lonely. It is that information, context, and eventually opportunity keep collecting around whoever is physically nearest to the decision — and no one ever decided it should work that way. Over a year, the gap stops being about information and starts being about careers. The people who were in the room got stretch work. The people who were not got told they need more visibility.

Step one: diagnose where proximity bias in hybrid work is doing your deciding for you
In the work I do with leadership teams, proximity bias almost never announces itself as unfairness. It shows up as three quieter patterns, and each one needs a different response.
Context. Real decisions get made in unscheduled moments—a walk to the parking lot, a chair pulled up to a desk—and then summarized rather than shared. The remote half of the team is always working from the summary.
Recall. When something urgent lands, you assign it to whoever comes to mind first. Presence is what makes people come to mind. This is the most consequential of the three and the least deliberate.
Read. You have far more casual data on the people you see. You know when they seem off, when they are stretched thin, when they are ready for more. For everyone else, you are working from status updates and guessing.
Here is a diagnostic worth doing on paper rather than in your head. List the last ten meaningful assignments you handed out — the visible ones, the ones that put someone in front of a client or an executive. Next to each name, write how often you see that person in person. If the pattern is obvious, you have your answer, and it is not a story about who is more capable.
Step two: change the habits that reward visibility over contribution
The adaptive part of the Rawe Applied Leadership Framework always begins with the leader rather than the policy, because a policy cannot fix a habit it never sees. Most leaders respond by mandating office days, which addresses the symptom by making everyone equally present and nothing else. The two changes that actually move it are smaller and harder.
The first is treating a hallway conversation as unfinished until you write it down. Not every exchange — only the ones where something got decided, reprioritized, or ruled out. If you decided it standing up, you owe the team four sentences sitting down. That single discipline removes most of the context gap, and it costs you about ninety seconds.
The second is slowing down the assignment reflex. When you feel the pull to hand something to the person standing in front of you, pause long enough to ask who else could do this, and who would grow from it. You will often land on the same person, and that is fine — the goal is not to redistribute work arbitrarily. The goal is for presence to stop being the tiebreaker you never knew you were applying.
Step three: build equal footing into the rhythm you already have
Hybrid charters and communication norms documents tend to fail for the usual reason: they live beside the work instead of inside it. The build phase attaches equal footing to things already on your calendar.
Give every recurring meeting one written home — a running notes doc where decisions land the same day. What matters is not the tool. It is that missing the room never means missing the decision.
When part of the group is remote, have everyone join from their own screen. Uneven audio and a half-visible whiteboard do more damage to participation than distance ever does.
Put deliberate one-on-one time with your least-seen people on the calendar at the same cadence as everyone else, and protect it harder. Proximity gives you those conversations for free elsewhere; here you have to schedule them.
Review assignment patterns once a quarter, the same way you review budget. Who has been in front of clients, executives, and new problems — and who has been quietly reliable somewhere you rarely look?
None of this requires a new hybrid policy or another platform. It requires a leader willing to accept that their sense of who is contributing is shaped heavily by who they happen to see, and to build a few small checks against that. Teams where this goes unaddressed rarely blow up. They just slowly sort themselves into an inner ring and an outer one, and the outer ring eventually stops trying — usually right before it starts leaving.
If you are reading this because someone on your team recently told you they feel out of the loop — or because you suspect they feel it and have not said so — that is worth a conversation. I work with leaders and leadership teams on exactly this kind of problem: the ones that look like logistics and turn out to be leadership habits. Reach out through the contact page and tell me what your team looks like right now. We will start there.




Comments