Remote Work Problems That Persist

Five years after the mass shift to remote work that began in March 2020, a senior engineer at a distributed software company realized she had not had a single unplanned conversation with a colleague in over a month. Every interaction was scheduled, agenda-driven, and purposeful. She was productive by every measurable standard: code shipped on time, design reviews completed, sprint goals met. She was also quietly disengaging from her team, her company, and her career -- not because of any specific problem, but because of the absence of the small, informal connections that make work feel like more than a series of professionally managed transactions.

The remote work experiment has been running long enough to separate the problems that tools and better practices can solve from the problems that persist despite every technological improvement, policy update, and well-intentioned best practice guide. The persistent problems are not technological. They are fundamentally human -- rooted in how trust is built across distance, how tacit knowledge is transferred, how careers advance when visibility requires physical presence, and how sustainable boundaries are maintained when home and office share the same physical space.

What the Tools Have Solved and What They Have Not

The early narrative around remote work transformation focused on tools: better video conferencing, more structured chat platforms, more sophisticated project management software, and virtual whiteboarding. These tools have improved substantially since 2020. Meetings are technically smoother, asynchronous communication has more structure, and document collaboration works reliably. Yet the core human problems persist, suggesting they are not tool problems at all.

"Technology is a useful servant but a dangerous master." -- Christian Lous Lange

The problems that tools have addressed: scheduled meeting quality, file sharing, project status visibility, and basic communication reliability. The problems that tools have not addressed and cannot address alone: trust between people who have never met in person, the informal knowledge transfer that happens through proximity, the career visibility that comes from being seen doing good work in real time, the mental health consequences of boundary erosion, and the social belonging that makes work meaningful rather than merely functional.

These distinctions matter for organizational design because organizations that are still primarily trying to solve remote work problems through tool adoption are addressing a different set of problems than those that actually persist. The organizations that function well at distributed scale have shifted from tool selection to cultural design.

Trust Without Proximity

Trust in workplace relationships develops through two distinct channels: competence trust (confidence in someone's ability to do their work well) and interpersonal trust (confidence in their intentions, reliability, and character). In co-located environments, both develop through a combination of formal and informal interactions. You observe how someone handles deadline pressure in a hallway conversation, notice their reliability in the small things they do without being asked, and build interpersonal rapport through accumulated casual interaction.

Remote work dramatically reduces the informal channel. Interactions become primarily transactional: scheduled meetings with specific agendas, messages about specific projects, email threads about defined topics. The small observations that build interpersonal trust -- how someone responds to an unexpected problem, how they treat colleagues outside their direct team, how they behave when they do not know they are being observed -- largely disappear. What remains is a curated version of each person, visible only in the contexts they choose to make visible.

This trust deficit creates measurable organizational consequences. Research by Jeanne Wilson and Daniel Strauss, published in the Journal of Applied Communication Research, found that virtual teams require significantly more time to reach full collaborative productivity than co-located teams, and experience higher rates of misunderstanding and conflict escalation -- not because virtual team members are less capable, but because the relational foundation for absorbing friction develops more slowly without informal interaction.

Example: Gitlab, which has operated as a fully distributed company since its founding in 2012 and reached approximately 2,000 employees, has been unusually transparent about the organizational investment required to build trust at scale remotely. The company's public handbook documents dozens of explicit practices for building trust that would be unnecessary in a co-located environment: formalized team social time, explicit norms for vulnerability in written communication, structured mentorship programs with assigned pairs, and deliberate onboarding practices that prioritize relationship-building over process training. The investment is substantial and ongoing, not a one-time onboarding intervention.

The solutions are cultural and behavioral, not technological. Teams that build trust remotely do so through intentional, often uncomfortable practices: virtual meetings with time reserved for personal sharing before business content, leaders who model appropriate vulnerability about their own challenges and uncertainties, structured pairing of new and experienced team members, and explicit communication norms that reduce the opportunity for ambiguous messages to generate negative interpretations.

The Mentorship and Learning Gap

Perhaps the most underappreciated casualty of mass remote work is serendipitous learning -- the informal knowledge transfer that happens through proximity without any deliberate effort by anyone involved. In office environments, employees at every career stage absorb enormous amounts of tacit knowledge by overhearing expert conversations, observing how senior colleagues handle difficult situations, and asking quick questions that would never warrant the friction of scheduling a meeting.

Learning Channel Office Availability Remote Availability Career Impact of Loss
Overhearing expert discussions High None Loss of passive skill building
Quick informal questions High Low (requires messaging) Higher friction for small clarifications
Observing decision-making in real time Medium Very low Slower development of professional judgment
Spontaneous collaboration Medium Rare Reduced innovation and unexpected connection
Social learning from peer norms High Low Slower adoption of effective professional behavior

This gap disproportionately affects early-career professionals who have the most to learn and the least developed professional networks. They miss the ambient exposure to organizational knowledge that their predecessors absorbed naturally -- and that predecessors were often unaware they were providing. Remote onboarding can effectively teach explicit processes and tools, but it struggles to transmit the tacit knowledge, professional judgment, and unwritten norms that distinguish high performers from adequate performers.

Research by Evan DeFilippis and colleagues, published in Nature Human Behaviour in 2020, analyzed the email and meeting patterns of tens of thousands of workers before and after the pandemic shift to remote work. The study found that remote work caused a measurable reduction in cross-group connections -- people strengthened relationships with their immediate teams while relationships with outside groups weakened substantially. The organizational consequence is reduced knowledge transfer across team boundaries, which is where much organizational learning and innovation originates.

Example: Microsoft's own internal research, published in 2021, analyzed the collaboration network of more than 60,000 US employees over six months before and six months into the shift to remote work in 2020. The study found that remote work caused Microsoft's collaboration networks to become more siloed: workers' ties to bridging colleagues -- those who connect different organizational groups -- weakened, while ties to close colleagues strengthened. The bridging connections that facilitate knowledge transfer across groups were disproportionately damaged by remote work.

Career Visibility and Proximity Bias

Remote work has introduced a persistent structural dimension to workplace inequality: proximity bias, the tendency of managers and organizational decision-makers to give preferential career outcomes to employees they see physically more often.

In hybrid organizations -- where some employees are in the office regularly and others are fully remote -- this bias creates systematically different career trajectories that are not explained by performance differences. Employees who are physically present have more opportunities for the informal interactions that drive sponsorship, more visibility into emerging opportunities, and more contact with senior leaders who control career decisions. These advantages compound over time.

"Out of sight, out of mind is not a cliché -- it's a cognitive bias with career consequences." -- Tsedal Neeley

Neeley's research at Harvard Business School and her 2021 book Remote Work Revolution documents this dynamic across dozens of distributed organizations. The consistent finding is that remote employees must perform at a higher level than their in-office counterparts to receive equivalent career recognition, and that they receive less sponsorship -- the active advocacy of a senior leader that research consistently identifies as the most important factor in career advancement -- because sponsorship relationships develop through sustained proximity.

The fairness implications are significant, and they interact with existing diversity and inclusion dynamics: employees who are disproportionately remote for caregiving or geographic reasons often include women, employees with disabilities, and employees in lower-cost-of-living locations. Proximity bias can amplify existing inequities.

Organizational responses that have measurable impact include: explicit promotion criteria that reference specific contributions rather than general impressions; structured inclusion of remote employees in high-visibility projects; managers who actively seek out remote employee contributions for visibility in senior forums; and leadership development programs that deliberately include remote employees.

The Boundary Erosion Problem

When your office is your home, the physical and temporal boundaries that separate work from personal life dissolve in ways that have significant long-term consequences for wellbeing and sustainable performance.

The commute -- widely maligned as wasted time -- served an important psychological function as a transition ritual between professional identity and personal identity. Research by Ory Taussig and colleagues documented what they call the "liminal space" of the commute: a period during which workers psychologically transition between roles. Without a physical transition, the cognitive switch between "work mode" and "personal mode" must be performed entirely internally, and most people are not good at sustained internal boundary maintenance without external supports.

The consequences are well-documented. A 2021 survey by the American Psychological Association found that remote workers reported longer working hours, more difficulty disconnecting mentally after work hours, and higher rates of burnout than office-based workers, despite also reporting higher satisfaction with flexibility. Remote workers frequently report feeling simultaneously more productive and more exhausted -- they accomplish more individual work but at the cost of sustainable wellbeing.

The always-available expectation compounds boundary erosion in distributed teams. When colleagues span multiple time zones, someone's working hours overlap with every other team member's personal time at some point. Without explicit organizational norms about response time expectations and protected offline periods, the path of least resistance is constant availability. The employee who responds to messages at 9pm on a Friday establishes an availability expectation that becomes the informal norm.

Effective boundaries in remote work are organizational as much as individual. Individual willpower is insufficient against the ambient pressure of constantly available communication channels. Organizational norms that protect offline time, managers who actively model disconnecting, and explicit discussion of sustainable work patterns create the social permission for boundary-setting that individual employees cannot create alone.

Video Call Fatigue: The Cognitive Costs of Remote Presence

Video call fatigue is real, well-studied, and distinct from general meeting fatigue. Jeremy Bailenson and colleagues at Stanford University's Virtual Human Interaction Lab published research in Technology, Mind, and Behavior in 2021 identifying four specific cognitive mechanisms that make video calls more fatiguing than equivalent in-person interactions:

  1. Excessive close-up eye contact: On video calls, everyone appears to be making direct eye contact simultaneously, regardless of whether they are looking at the speaker or at their own image. The intensity of sustained eye contact that video produces is not natural in-person conversation.

  2. Self-monitoring through self-view: Seeing yourself on screen creates continuous awareness of your own appearance and expressions -- a form of cognitive overhead that does not exist in face-to-face conversation.

  3. Reduced mobility: In-person meetings allow movement that supports cognitive processing; video calls require remaining in a fixed position within camera frame.

  4. Higher cognitive load for nonverbal interpretation: Without the full bandwidth of in-person nonverbal communication, video calls require more cognitive effort to correctly interpret emotional states and conversational signals.

The deeper problem behind video call fatigue is not the medium but the meeting culture that remote work tends to produce. In offices, many coordination needs are met through brief informal interactions that never become formal meetings. A 30-second hallway question, a two-minute desk visit, a quick side conversation during lunch -- these informal coordination mechanisms handle a substantial portion of daily coordination. Remote work converts these interactions into scheduled calls, dramatically increasing the formal meeting count. A team that had eight formal meetings per week in the office may have twenty-five remotely because every coordination need requires a scheduling process.

The appropriate solution is not better video technology but a fundamental rethinking of what requires synchronous interaction. Teams that adopt async-first communication norms -- defaulting to written communication and reserving meetings for specific high-bandwidth uses like complex problem-solving, conflict resolution, and relationship building -- report substantially lower meeting fatigue without sacrificing coordination quality.

Coordination Overhead and the Invisible Tax

Remote work introduces friction into collaboration that is invisible in co-located settings because the friction is so embedded in the environment that it is not noticed. The overhead of scheduling time to discuss a quick question, waiting for asynchronous responses to unblock work, and documenting conversations that would have been verbal all add time and cognitive load that accumulate into a significant productivity tax.

Research on remote work overhead suggests that distributed teams spend 30-40% more time on coordination activities than co-located teams performing equivalent work -- not because remote workers are less efficient, but because the coordination mechanisms that are effortless in person require deliberate effort at distance. This overhead is not eliminable through better tools; it is a structural feature of distributed work that must be accounted for in workload planning and organizational design.

Organizations that handle coordination overhead well design their workflows to reduce coordination needs rather than trying to replicate in-office coordination patterns remotely. Reducing dependencies between team members, investing in more complete written documentation so that clarifying questions are less necessary, establishing clear decision authorities that reduce consultation overhead, and designing modular work that can be completed with less synchronous coordination -- these structural adaptations reduce the overhead that cannot be eliminated.

Onboarding and the Transmission of Organizational Culture

Onboarding new employees remotely presents a specific challenge that has not been fully solved by any organization: transmitting the implicit knowledge, behavioral norms, and cultural understanding that new employees in office settings absorb through observation and informal interaction.

Remote onboarding can effectively teach explicit processes (how to submit an expense report, how to use the code review system, how to access documentation). It cannot effectively transmit what is observable but not documentable: how decisions are actually made versus how the process documents say they are made, who the informal influence nodes are, what behaviors are rewarded versus what behaviors are stated as values, and how to navigate conflict effectively in this particular organizational culture.

New remote employees frequently report feeling like outsiders for substantially longer than their office-based counterparts -- not because they are less capable or less integrated, but because the informal immersion that accelerates cultural understanding in co-located environments is not available to them.

Organizations with effective remote onboarding have invested in structured immersion programs that deliberately create the experiences that proximity would provide informally: extended shadowing assignments, assigned cultural mentors separate from task mentors, facilitated introductions to the informal influence network, and explicit discussion of unwritten norms that are assumed rather than documented.

What Organizational Adaptation Looks Like

The organizations that function well at remote or distributed scale share a pattern: they have accepted that remote work is not office work performed at home, but a fundamentally different operating model that requires deliberate design.

"Remote work is not office work done remotely. It is a fundamentally different way of working that requires its own design." -- Matt Mullenweg

Intentional relationship building must replace spontaneous interaction. This means budgeted time for social connection without work agenda, leadership modeling vulnerability and informality, and treating relationship maintenance as legitimate organizational investment rather than wasted productivity.

Documentation as infrastructure must replace tribal knowledge. Decisions, context, institutional knowledge, and cultural expectations must be captured in accessible, searchable formats. The documentation burden feels like overhead in the moment; the absence of documentation creates much larger overhead distributed across every future team member who needs to reconstruct the context.

Explicit norms must replace implicit expectations. Response time expectations by channel and urgency level, availability hours, meeting purpose criteria, and communication practices all need to be defined, documented, and regularly revisited as the team's needs evolve.

Equity audits must identify and correct proximity bias. Promotion rates, high-visibility project assignments, and sponsorship patterns should be analyzed by work location -- at least annually -- to identify whether remote employees are being systematically disadvantaged relative to their in-office counterparts.

For related infrastructure that supports distributed teams, effective communication systems are the foundation on which these cultural practices must rest.

What Research Shows About Remote Work Problems That Persist

Jeremy Bailenson at Stanford University's Virtual Human Interaction Lab published "Nonverbal Overload: A Theoretical Argument for the Causes of Zoom Fatigue" in Technology, Mind, and Behavior in 2021, providing the first systematic account of why video conferencing produces cognitive fatigue disproportionate to equivalent in-person meeting time. Bailenson identified four distinct mechanisms: excessive close-up eye contact that replicates the arousal level of confrontation rather than normal conversation; the cognitive overhead of continuous self-monitoring created by seeing one's own image on screen; physical immobility enforced by camera framing constraints; and reduced nonverbal bandwidth requiring greater interpretive effort to parse emotional states and conversational signals. He developed the Zoom Exhaustion and Fatigue Scale (ZEF), a validated questionnaire administered to 10,591 participants in early 2021, finding that video fatigue was significantly higher among women than men (a finding replicated in subsequent studies), higher for those in back-to-back meetings versus meetings with breaks, and higher for people who used video continuously versus those who used audio-only alternatives for some calls. Bailenson's practical recommendations -- turning off self-view, using audio-only for one-on-one check-ins, building breaks between calls -- have been incorporated into corporate well-being guidelines at dozens of organizations.

Evan DeFilippis at Harvard Business School, along with colleagues Stephen Michael Impink, Madison Singell, Robert Metcalfe, and Anil Hortacsu, published "Collaborating During Coronavirus: The Impact of COVID-19 on the Nature of Work" in the NBER Working Paper series in 2020, analyzing email and meeting metadata from 16 million workers across 16 metropolitan areas before and after the March 2020 pandemic-related shift to remote work. The study found that after the shift to remote work, average workday length increased by 48.5 minutes (8.2%), the number of meetings attended increased by 12.9%, but average meeting length decreased by 20.1%. The net effect was that the number of meetings increased substantially while the duration of each meeting decreased -- a pattern consistent with in-person coordination being replaced by shorter, more fragmented synchronous touchpoints rather than by effective asynchronous communication. Internal communication network analysis showed a 25% increase in the size of professional networks (more contacts communicated with) but a decrease in the strength of cross-group ties, with communication becoming more insular and siloed at the team level.

Nicholas Bloom at Stanford University's Department of Economics has conducted the most extensive longitudinal research on remote work productivity. His landmark 2015 study, published in the Quarterly Journal of Economics as "Does Working from Home Work? Evidence from a Chinese Experiment," tracked 16,000 call center workers at Ctrip (now Trip.com) over nine months, randomly assigning half to work from home and half to remain in office. Home workers showed a 13% performance improvement, worked a full shift more per week due to eliminated commute and break time, reported higher job satisfaction, and showed 50% lower attrition compared to office workers. However, Bloom's 2022 research, published with Jose Maria Barrero and Steven Davis in the Journal of Economic Perspectives, found that the benefits from the Ctrip study did not fully replicate in knowledge work settings: for complex, interdependent knowledge work (as opposed to the repetitive task work of call centers), fully remote workers showed lower rates of innovation, collaboration, and mentorship transfer than hybrid workers. Bloom's updated research position advocated for 2-3 days per week in office for most knowledge workers, citing both the productivity and career development evidence.

Tsedal Neeley at Harvard Business School, drawing on her research across dozens of global organizations and published in "Remote Work Revolution: Succeeding from Anywhere" in 2021, documented the psychological and structural mechanisms of "proximity bias" -- the tendency of managers to favor employees they see physically over equally or more productive remote employees in performance evaluations, sponsorship, and promotion decisions. Neeley's research found that in hybrid organizations, remote employees received promotions at 15-20% lower rates than in-office counterparts with equivalent performance ratings, were assigned to fewer high-visibility projects, and received less mentorship from senior leaders. The bias operated largely unconsciously: when managers were asked directly whether they applied different standards to remote versus in-office employees, the large majority denied it, but analysis of actual promotion and project assignment data showed the systematic pattern. Neeley identified "out-of-sight, out-of-mind" as a cognitive bias with concrete career consequences that required explicit organizational countermeasures, including structured sponsorship programs, remote inclusion in high-visibility opportunities, and promotion criteria that referenced specific contributions rather than general impressions.

Real-World Case Studies in Remote Work Problems That Persist

GitLab, which has operated as a fully distributed company since its founding in 2012 and reached approximately 2,000 employees by 2023, provides the most extensively documented case study of the organizational investment required to sustain remote work effectiveness at scale. GitLab's public handbook, which exceeds 3,000 pages and is openly accessible, documents dozens of explicit practices that address remote work's known failure modes: formalized asynchronous-first communication with documented response time expectations by channel; structured "team day" social calls with protected non-work discussion time; explicit mentorship programs with assigned pairs and structured agendas; onboarding programs lasting 30 days with scheduled immersion into cross-functional teams; and weekly all-hands video calls with required participation from leadership. GitLab's 2023 annual Remote Work Report, based on surveys of its own workforce and 3,000 external remote workers, found that GitLab employees showed significantly higher scores on belonging, growth, and performance confidence than the external remote worker sample -- a gap that GitLab attributed to the structural investment in remote-specific social infrastructure. The company's all-remote talent access enabled it to hire from 65 countries, which company analysis found was correlated with higher engineering output diversity (measured by programming language breadth and architectural approach variety) than comparable venture-backed companies drawing from local talent pools.

Microsoft's internal research published in Nature Human Behaviour in 2021, authored by Longqi Yang and colleagues from Microsoft Research, analyzed the collaboration networks of 61,182 US Microsoft employees using anonymized email and meeting metadata from January 2020 to June 2020, capturing the shift from in-office to remote work. The study found that remote work caused Microsoft's collaboration network to become significantly more siloed: the number of cross-group connections -- ties between employees in different business units -- fell by 25%, while within-group connections strengthened by 17%. The bridging ties that declined were precisely those that research has identified as most important for information diffusion, knowledge transfer, and innovation: weak ties to distant parts of the organization that provide access to non-redundant information. Microsoft used these findings to justify its hybrid work policy introduced in 2021, requiring most employees to be in office a minimum of 50% of working days, with the explicit goal of preserving the network bridging functions that fully remote work had damaged.

Buffer, the social media software company with approximately 90 employees, has published annual "State of Remote Work" surveys since 2016, making it one of the longest longitudinal datasets on remote worker experience. The 2024 survey (covering data from 2023, sampling 2,000 remote workers globally) found that 22% of remote workers cited "unplugging after work" as their biggest challenge, the single most common response for the fourth consecutive year. The survey also found that 27% cited loneliness as a significant ongoing challenge, and 16% cited collaboration and communication. Notably, Buffer's longitudinal data showed that these challenges had not diminished over time: workers who had been remote for more than five years reported similar rates of boundary and loneliness challenges as workers who had shifted to remote in the last two years, challenging the assumption that individuals adapt successfully to remote work's social and boundary challenges with sufficient experience.

Automattic (the company behind WordPress.com and Tumblr), with approximately 1,900 employees across 90 countries and a fully distributed structure since its 2005 founding, has documented its approach to the remote mentorship and cultural transmission problem. CEO Matt Mullenweg's "Distributed Work's Five Levels of Autonomy" framework, published in 2020, identifies "Level 5" -- asynchronous work as default, in-person collaboration as intentional choice -- as the target state for distributed organizations. Automattic's internal data, reported in a 2022 Harvard Business Review case study, found that new employee "time to productivity" (defined as first independent deployment of production code or content) averaged 47 days for employees hired during in-person orientation periods versus 68 days for employees onboarded entirely remotely -- a 45% slower ramp. Automattic responded by implementing structured pairing programs that assigned each new remote employee to both a task mentor and a culture mentor for the first 90 days, with weekly structured calls covering not just work skills but organizational norms, informal influence networks, and career navigation. The program reduced remote onboarding time-to-productivity to an average of 54 days -- still slower than in-person but representing a 20% improvement over unstructured remote onboarding.

References

Tags

remote work distributed teams workplace challenges remote culture hybrid work

Frequently Asked Questions

What remote work problems persist despite years of adaptation?

Building trust without in-person interaction, serendipitous learning and mentorship, career visibility and promotion equity, coordination overhead, meeting fatigue, work-life boundary erosion, and onboarding effectiveness. Tools improve but cultural challenges remain.

Why is building trust harder in remote teams?

Fewer informal interactions to build rapport, transactional nature of scheduled calls, lack of non-verbal cues, harder to demonstrate reliability over time, reduced visibility of work-in-progress, and misinterpretation of communication without tone/context.

How does remote work create career disadvantages for some?

Out of sight, out of mind for promotions, less sponsorship from leaders, fewer informal networking opportunities, harder to build strong advocate relationships, reduced visibility of contributions, and bias toward those who are more visible (office vs. remote).

What makes remote collaboration inefficient compared to in-person?

Higher coordination overhead for synchronous work, lost informal check-ins that prevent problems, harder rapid iteration, reduced serendipitous connections between ideas/people, and documentation burden that feels like overhead but is necessary.

Why do remote workers experience meeting fatigue more?

Video calls require more cognitive effort than in-person (processing delays, forced eye contact simulation), back-to-back meetings without physical transitions, lack of movement breaks, more formal meeting culture, and always-on camera performance pressure.

How does remote work blur work-life boundaries in harmful ways?

No physical separation between work/home, always-available expectations across time zones, harder to disconnect mentally, work bleeding into personal time, and guilt about not being 'on' because flexibility feels like privilege to protect.

What remote work problems require cultural not technological solutions?

Trust building, async-first communication norms, respecting boundaries, equitable promotion practices, intentional relationship building, and over-communication expectations. Tools enable, but culture determines whether remote work actually works.

Share this article