David R. Longnecker

Most hybrid teams think they’re integrated, and the logistics of modern remote work make that easy to believe. Shared tooling and common meeting cadences give everyone the sense of working as one unit. But integrated means something different than co-located-accessible. What distributed teammates often experience is something messier — technically included but not equally positioned.

The gap between hybrid and integrated isn’t about technology or policy. It’s a distance bias problem, and most organizations are actively maintaining it without realizing it.

Evaluation System Bias

Remote workers are promoted 31% less often than people who work in an office, and are 38% less likely to receive bonuses, according to Live Data Technologies’ analysis of more than two million employees. Separately, in Owl Labs’ 2024 State of Hybrid Work report, 55% of respondents said their managers view office workers as more trustworthy and harder-working — not because of performance data, but because of proximity (they “see the work happening”).

Distance bias is the tendency to unconsciously favor people and things that are physically closer. What’s striking isn’t that it exists, but how thoroughly it persists after five-plus years of normalized hybrid work. Organizations adopted the logistics of distributed collaboration but not the cultural and structural changes that would make it equitable. Most performance evaluation systems still implicitly reward presence because that’s what they were designed to measure when “work” and “office” were synonymous.

The compounding effects are easy to miss. Remote workers who feel less visible, speak up less, get tagged for fewer high-profile decisions, and fall behind in the informal sponsorship networks that actually drive advancement. Nobody intends this outcome. It’s the default output of structures built for physical co-location that haven’t been redesigned.

What “Together” Time Actually Does

The instinct when a distributed team finally occupies the same physical space is to maximize productive output. There’s a backlog of decisions and roadmap conversations that feel easier in person, and a general sense that because the time is expensive and rare, it should be efficient. Most organizations treat company gatherings this way, packing agendas until the offsite looks more like a compressed sprint than a retreat.

What gets missed is that in-person time serves a fundamentally different function for a distributed team. The working relationship between remote colleagues who’ve never experienced each other as three-dimensional people has a ceiling. Information exchange can happen asynchronously. The kind of trust formation that enables honest disagreement and confident collaboration across time zones generally can’t be scheduled as a meeting agenda item.

There’s also something worth naming about why decisions feel easier in person. Some of that is real. Spontaneous back-and-forth and shared context are genuinely hard to replicate across a Zoom grid. But part of it is social pressure. Face-to-face, the cost of dissent is higher. It’s harder to push back on a leader sitting across the table than to flag a concern in writing before the meeting.

In my own experience running both, structured async input tends to surface disagreement that a synchronous meeting quietly buries, because writing a dissenting comment carries less social cost than speaking one out loud in the room. Remote doesn’t just reduce presence. In some conversations, it increases honesty.

I was lucky enough back in the 2010s to work for an organization that got it right. We were all remote, but had regular retreats where we left work at the door. We’d spend time getting to know each other as people, philosophizing about the future each of us wanted and how we’d ensure we make that happen with the organization.

The work got done asynchronously, and the retreats were for connection. The result was a team that felt deeply integrated even though we were distributed. We had the tools to do the work, but we also had the relationships to do it well.

The productivity and retention gains I’ve seen on well-integrated distributed teams track back to that relational foundation, not to deliverables produced while everyone happened to be in the same room.

Integration Looks Different

Remote workers average 4.55 hours of daily focus time versus 3.72 hours for in-office peers, a 22% gain that comes directly from fewer interruptions (Hubstaff, 2024). The forced check-in that feels like a quick 15-minute sync carries a much higher cost in focus recovery. Compounded across a year, that recovery time adds up to roughly 62 hours per employee.

This doesn’t mean remote workers need less management. It means they need different management, built around async-first workflows and explicit decision documentation, with outcomes as the primary signal rather than visible activity. The distinction matters because most hybrid environments don’t make it. They layer remote workers into the same management cadence designed for in-office teams, treating asynchronous work as a workaround rather than an intentional design choice.

This applies equally to globally distributed teams where the “remote workers” are entire engineering organizations in India, Eastern Europe, or Latin America. The cadence problem doesn’t change with geography or culture, but the time zone overlay compounds it further. A meeting timed for headquarters’ morning is already someone else’s evening, and the cadence rarely gets redesigned around that fact.

There’s an honest counterpoint. Employees who fully self-determine their own hybrid schedules are 76% more likely to report burnout as their primary challenge, per Gallup. Autonomy without structure creates its own dysfunction. Integration isn’t “leave them alone and trust the output.” It requires building systems that function regardless of location.

Where This Sits

MIT Sloan’s framing is worth a read, and then a re-read. Leaders are treating hybrid as a policy challenge when it’s actually a leadership capability challenge. Organizations that are genuinely good at distributed work aren’t the ones with the best attendance policies. They measure results rather than presence, and they build evaluation systems that don’t implicitly penalize remote workers for their location. Integration is something those organizations designed, not assumed.

That’s a different capability than most senior leaders have been asked to develop. “Badge tracking” is concrete and reportable, but designing evaluation systems that don’t implicitly favor proximity is messier, and rebuilding how in-person time gets used requires overcoming deeply ingrained assumptions about what makes shared time “productive” in the first place. These are harder problems to manage.

But they’re where the modern workforce’s problem actually lives.

I wrote about the RTO trust paradox last year. Distance bias is what persists when the mandate debate is over and the team still doesn’t feel integrated.

Most teams are already hybrid. The harder question is whether integration got designed or just assumed. Five years in, the data suggests we’ve mostly done the latter.