Hybrid teams — some days in an office, some days remote, often with different individuals choosing different patterns — face a trust challenge that's distinct from either a fully remote or fully in-person team's: the risk of a visible, if unintentional, split between people who are seen more often in person and people who aren't, which can subtly and unfairly shape perceptions of who's actually working hard, independent of any real difference in output. For further background, consult APA healthy workplace resources.
The specific risk hybrid arrangements introduce
Proximity bias — the well-documented tendency to rate people who are physically visible more favorably than equally productive people who aren't, simply because visibility itself gets misread as evidence of effort or commitment — is a genuine risk in hybrid arrangements specifically, more so than in a fully remote team where nobody has an in-person visibility advantage over anyone else. Left unaddressed, this can quietly disadvantage employees who work remotely more often, regardless of their actual output, which is both an unfairness problem and, eventually, a retention risk for exactly the flexibility that made hybrid arrangements attractive in the first place.
The insidious part of proximity bias, worth naming directly, is that it doesn't require any conscious unfairness on a manager's part to produce a real, measurable effect — it operates largely below the level of deliberate judgment, through the simple, well-documented cognitive tendency to weight recently and frequently observed information more heavily than information encountered less often. A manager who would sincerely deny favoring in-office employees can still, without any awareness of doing so, form a more favorable general impression of someone they happen to see and interact with in person more often, purely as a byproduct of familiarity rather than any actual assessment of comparative output.
Why data alone doesn't neutralize a bias operating outside conscious awareness
It might seem that objective, data-driven metrics — the kind discussed throughout this site — would straightforwardly correct for proximity bias, by giving managers an outcome-based alternative to informal, presence-based impressions. In practice, data doesn't fully neutralize the bias unless a manager deliberately checks their own informal impression against it; a manager can review outcome data that shows no real difference between two employees and still walk away with a stronger, more favorable general impression of the one they see in person more often, if the data review isn't paired with an explicit, deliberate step of checking that impression against the numbers rather than simply confirming it.
- Apply the same evaluation criteria and the same access to opportunities regardless of in-office frequency — explicitly, since proximity bias operates largely unconsciously and doesn't announce itself to the person exhibiting it.
- Where workforce data (attendance, project time allocation) is used at all, apply it consistently regardless of whether someone works primarily in-office or remote — inconsistent standards between the two groups tend to compound, not offset, proximity bias.
- Make meeting and decision-making processes equally accessible regardless of physical presence — a decision effectively made in an in-person hallway conversation, then merely announced to remote participants afterward, structurally disadvantages the remote half of a hybrid team regardless of anyone's individual intent.
- Periodically check outcome data (promotions, project assignments, performance ratings) for a pattern correlated with in-office frequency rather than with output — a concrete, checkable way to catch proximity bias before it becomes an entrenched pattern.
- When reviewing outcome data specifically to counter an informal impression, do so deliberately and explicitly — simply having the data available doesn't correct the bias unless it's actually used as a deliberate check rather than passive background information.
- Train managers specifically on proximity bias as a named, well-documented pattern, rather than assuming general fairness training adequately covers this particular, hybrid-specific risk.
Why this connects back to the wider theme of this site
The fix for proximity bias isn't more monitoring of remote employees to “prove” their productivity — that response treats the remote half of a hybrid team as needing to overcome a deficit of trust the in-office half doesn't face, which reinforces the very asymmetry the problem is about. The more durable fix is consistent process and deliberate, explicit use of whatever outcome data already exists, applied the same way regardless of where someone happens to be sitting on a given day — which is the same consistency and transparency theme running through nearly every guide across this site, applied here to a bias that's specific to the hybrid arrangement itself. A related discussion is available the source.
This connects to a theme running throughout this site's resources: consistency and transparency, applied deliberately rather than left to default assumptions, tend to be the most reliable tools available for keeping any team's trust intact — hybrid arrangements just introduce a specific, well-documented way that default assumptions can go quietly wrong.