Two weeks ago a senior engineer in Berlin told me she had not been looped into a product strategy call. Six weeks later the same engineer received a promotion nomination for a colleague who joined the team from our San Francisco office — someone she had never spoken to outside a shared Slack channel.
I have spent eight years building products with remote and hybrid teams, from a two-person startup in Lisbon to engineering squads spread across FAANG. Proximity bias is the tax most hybrid teams pay without writing an invoice for. It does not appear on any performance dashboard. It hides in who gets the visible project, who remembers to grab the good seat on the strategy call, who gets the small favor before the big favor.
If you have never noticed it, it is happening to you right now.
How Proximity Bias Hijacks a Hybrid Team
Proximity bias is not an HR word. It is a brain bug. Neuroscientist William Mobbs at UC Berkeley has described it as a preference for familiar faces that is hardwired rather than a policy failure. When you cannot see someone’s face, your brain quietly lowers their availability to your attention, and your attention is what decides which problem they solve and which promotion they get.
Three symptoms show up on every hybrid team I have audited in the last year:
- Project visibility. The best and highest-leverage work flows to whoever is in the room, whether that means a physical office or the shared working hours of a time zone.
- Decision latency. Informal decisions happen in the corridor, at lunch, or in the last ten minutes of a call. Remote colleagues find out about them on Slack.
- Promotion asymmetry. Stanford’s 2024 hybrid-work study of more than 400 firms found that remote employees were 40% less likely to be promoted than in-office peers at the same level.
I want to stress that these are not always malice. Most people in the room do not think about it. That is exactly why we need systems, not slogans.
An 8-Point Diagnostic Checklist
Before you spend a quarter designing rituals, spend one afternoon measuring the current state. Copy this checklist into a Google Doc and share it with your manager group. It is not a score. It is a starting conversation.
| # | Diagnostic question | Red flag signal |
|---|---|---|
| 1 | Where did your last 20 project leads come from? | More than two-thirds from one office or time zone |
| 2 | When was the last time a fully remote engineer got promoted? | More than 12 months ago |
| 3 | What percentage of decisions are written in a shared doc? | Under 50% |
| 4 | How many team members never attended the last all-hands? | Anything above 10% of the team |
| 5 | Do you keep a list of who works where in the leadership group? | No |
| 6 | What is the ratio of Slack threads to 1:1s in a given week? | Fewer than 3:1 (too many sync conversations) |
| 7 | What is your team’s average onboarding feedback score for remote new hires? | Below 4 out of 5 |
| 8 | How often does the CTO skip the weekly meeting? | Weekly, and skipped attendees get no meeting notes |
If four or more rows are red, you are not running an async team. You are running an office with a video bridge on top. Fix the shape first, then fix the rituals.
Five Cross-Timezone Rituals That Fight Proximity Bias
I have tried dozens of rituals across teams between 10 and 200 people. These are the five that survived multiple quarters of testing without turning into checkboxes.
Ritual 1: Async All-Hands With a Rotating Owner
Every Monday morning a rotating team member writes a four-paragraph update in a shared doc. Paragraphs cover what shipped, what is blocking, what the team is deciding this week, and what changes. Anyone in any time zone reads the same doc at 9am their own time.
No one is allowed to add a but-we-also-discussed-this-in-the-all-hands-call follow-up. The doc is the meeting. This is the single largest behavioral shift in reducing proximity bias that I have measured.
Ritual 2: Monthly Cross-Timezone 1:1 Pairings
Every month, managers pair each in-office person with a remote colleague from a different time zone for a 30-minute 1:1, and vice versa. No agenda beyond: tell me what the team feels like from where you sit.
This has zero productivity value on paper. It is the reason I have seen teams close the promotion gap fastest, because the person giving the review has talked to the person receiving it at least once outside their time zone.
Ritual 3: Quarterly Retro Write-Ups, Not Calls
Every quarter each squad writes a two-page retro. It goes to every other squad and gets two weeks of async comments. Only the write-up is archived. If you skip this, you are telling remote contributors that the memory of your team lives in a specific office.
Ritual 4: Rotating Decision-Log Ownership
Someone owns the decision log. Not the CEO, not the manager. A rotating role that a junior engineer can hold. Their job is to catch every we-just-decided-that moment in chat and turn it into a doc.
The role is also your proximity bias detector. If decision-log owners are always senior engineers in one location, you know exactly where the bias lives.
Ritual 5: Async Promotion Evidence Windows
In the four weeks before each promotion cycle, every candidate submits a written case study covering what they shipped, what they unblocked, and what they mentored. Reviewers read these asynchronously.
This does not prevent proximity bias from existing. It stops proximity bias from being the primary input to the promotion decision.
Track Culture Health in Your OKRs
Culture health metrics are not vibes. They should be an OKR row you can defend to the board.
| Metric | Definition | Target | How to collect |
|---|---|---|---|
| Project distribution | Share of high-visibility projects by location | Within ±20% of headcount split | Project tracker tags |
| Promotion latency | Months between tenure cohort and first promotion | No more than 6 months apart between cohorts | HRIS plus Slack archive |
| Decision doc ratio | Share of decisions captured in docs | Above 80% | Weekly doc diff |
| Async read rate | Share of weekly updates read by all staff | Above 90% | Notion page views |
| 1:1 completion | Share of scheduled 1:1s completed | Above 95% | Calendar audit |
| Remote NPS | eNPS from remote-only staff | Positive | Quarterly pulse survey |
I would recommend reviewing this table monthly in your leadership group. The numbers will not look great at first. That is the point.
A Bias Review Checklist for Promotions
Promotion reviews are the moment proximity bias is most expensive to leave unchecked. Run this checklist as a mandatory step in every promotion packet.
- Who is on the promotion review committee? If the committee is fully from one location, that is your first signal. Rotate at least one remote-only reviewer into every committee.
- How much evidence is written versus verbally recalled? Anything above 30% verbal evidence is a red flag. If it was not written down, it did not happen.
- What is the promotion velocity by location? Pull it, compare it, and if remote peers take 6 months longer to reach the same level, ask why.
- Whose informal work counts? Documentation, mentorship, community building, incident response — all real work, and disproportionately done when you are not in the room.
- Are remote candidates getting the same scope in their last quarter? Not the same hours, the same scope.
- Can every committee member name two remote contributors who moved this quarter? If they cannot, they were not paying attention.
Proximity bias is not a moral failing of a team leader. It is a physics problem. Fix the environment, not the intent.
Where to Start Next
Pick one ritual this week. Measure it in eight weeks. If your team has never tried anything, start with the async all-hands. It is the cheapest and the fastest to feel. The point is not to fix proximity bias by the end of the quarter. The point is to build the muscle that fixes it before it decides who leaves next.
If your team is already past that stage, focus on the promotion checklist first. It is the one place where proximity bias shows up directly on the payroll.