Pew Research on Remote and Hybrid Work: What Workers Actually Report
Kinetiq Team
The debate about remote work has generated more opinion than evidence. But the Pew Research Center, which surveys tens of thousands of workers and does not sell consulting services or software, provides some of the cleanest data available. And what workers actually report challenges several popular narratives.
The core numbers: approximately 35% of workers with remote-capable jobs are working from home full time. About 60% want to work from home all or most of the time. The majority cite productivity benefits. And managers and employees differ significantly in their perceptions of how well remote work is functioning. That last data point is the one that deserves the most attention.
What the Research Shows
Remote Work Has Stabilized, Not Reversed
Despite three years of return-to-office headlines, Pew’s data shows that remote work has stabilized at a level well above pre-pandemic norms. Roughly 35% of remote-capable workers remain fully remote, and the majority of remote-capable workers operate in some form of hybrid arrangement. The wholesale return to five-day office work that many executives predicted has not materialized.
This stabilization is not inertia. It reflects a structural equilibrium. Workers who can do their jobs remotely have demonstrated that they can, and both their productivity data and their stated preferences reinforce the arrangement. The organizations still fighting this reality are spending political capital on a battle the data suggests they have already lost.
Workers Report Productivity Benefits
A majority of remote workers in Pew’s surveys cite productivity as a benefit of working from home. This aligns with the Stanford research from Nick Bloom, which finds that hybrid work reduces attrition by approximately 35% with minimal productivity impact, and that structured hybrid arrangements outperform unstructured flexibility.
The productivity finding is notable because it directly contradicts the most common management objection to remote work. Workers are not reporting that they slack off at home. They are reporting that they get more done. Whether this reflects fewer interruptions, reduced commute fatigue, greater schedule control, or some combination varies. But the pattern is consistent across multiple survey waves.
The Preference Gap Is Clear and Stable
About 60% of workers with remote-capable jobs want to work from home all or most of the time. This is not a pandemic hangover. It is a settled preference that has remained stable across multiple survey periods. Workers have experienced remote work, evaluated it against office work, and made their assessment. The preference data is not ambiguous.
This creates a strategic reality for employers. Organizations mandating full return-to-office for remote-capable roles are operating against the stated preferences of the majority of their workforce. The Buffer State of Remote Work report confirms this from a different angle: 98% of remote workers want to continue working remotely at least some of the time. The demand signal is overwhelming.
The Manager-Employee Perception Gap
Pew’s most important finding may be the significant gap between how managers and employees perceive remote work effectiveness. Managers are substantially more likely to express concerns about productivity, collaboration, and culture in remote settings. Employees are substantially more likely to report that remote work is going well.
This is not simply a disagreement. It is a coordination signal. When managers and employees have fundamentally different assessments of the same arrangement, the problem is not that one side is wrong. The problem is that both sides are operating with different information, different metrics, and different definitions of success. That is a systems problem, not a trust problem.
Why This Matters for Teams
The Pew data matters for teams because it reframes the remote work question from “Should we allow it?” to “How do we make it work?” The first question is settled by preference data and market forces. The second question is an operational design challenge.
The manager-employee perception gap is the clearest signal. When a manager says “I am not sure my team is productive” and the team says “We are more productive than ever,” the issue is not deception or delusion on either side. The issue is that there is no shared system for making work visible. The manager cannot see what the team is doing. The team knows what they are doing but has no structured way to demonstrate it. Both are frustrated. Both are right, from their own vantage point.
This is why the async norms conversation matters so much in hybrid and remote contexts. Without explicit agreements about how information flows, how progress is communicated, and how coordination happens across time zones and schedules, every participant fills the gaps with assumptions. Managers assume the worst. Employees assume their work speaks for itself. Neither assumption is productive.
The Asana Anatomy of Work Index provides the operational evidence: workers spend 58-60% of their time on “work about work,” including coordination, searching for information, and duplicated effort. In distributed settings, this coordination tax is even higher. The teams that manage it well are not the ones with the best technology. They are the ones with the clearest operating norms.
The Gap the Data Reveals
Pew’s research is rigorous and representative. It tells us what workers experience and prefer. What it does not address is the infrastructure question: what do teams and organizations need to build to make remote and hybrid work function at a high level?
The perception gap between managers and employees is the most actionable finding in the data, but Pew does not prescribe how to close it. This gap is not unique to remote work. It exists in every setting where work is not visible by default. In an office, managers can see people working (or at least present). Remote work removes that visibility, exposing the fact that most teams never had a real system for tracking and communicating progress. They had proximity, and they mistook it for coordination.
The research also surfaces a tension around flexibility. Workers want flexibility, but the most effective remote arrangements, according to both Pew and the Stanford data, are structured rather than fully autonomous. Fixed remote days, regular synchronous touchpoints, and explicit communication norms outperform “work whenever and wherever.” This means the answer to remote work is not maximum freedom. It is intentional design.
The compliance and coordination risks in distributed teams add another layer. As teams become more distributed and adopt more AI tools, the need for explicit operating norms increases. Who reviews AI-generated work? How are handoffs managed across time zones? What decisions require synchronous discussion? These questions do not answer themselves, and in fully distributed settings, the cost of leaving them unanswered is higher.
What This Looks Like in Practice
The practical implication of the Pew data is clear: remote work succeeds when systems exist, not when trust is assumed. The teams reporting the highest satisfaction and productivity in remote settings are not the ones with the most permissive policies. They are the ones with the most explicit operating agreements.
Closing the manager-employee perception gap requires three specific systems. First, a shared definition of “done” for each work product. When everyone agrees on what complete looks like, progress becomes visible without surveillance. Second, a regular communication rhythm that makes work status transparent without requiring meetings. Async updates, shared dashboards, and documented decisions replace the informal hallway conversations that offices provided for free. Third, explicit norms for when synchronous communication is required and when async is sufficient. Without this, teams default to either too many meetings (the office reflex) or too little coordination (the remote default).
These are not abstract recommendations. They are the specific systems that differentiate high-performing distributed teams from struggling ones. The Stanford research confirms the pattern: structured hybrid outperforms unstructured flexibility. Structure is the variable, not location.
At KINETIQ, this is the core design principle behind KINETIQ Sync, which focuses specifically on the habits and systems that distributed teams need: async communication norms, channel selection frameworks, meeting design, boundary management, and visibility practices. These are the operational capabilities that the Pew data shows are missing. Workers want remote. Managers want visibility. The system that satisfies both is not a policy. It is an operating framework.
KINETIQ Foundations addresses the underlying capabilities that make any work arrangement function: clear communication, structured decision-making, disciplined execution, and effective handoffs. These capabilities matter in an office. They matter more when the team is distributed, because there is no ambient context to compensate for their absence.
The Pew data does not tell organizations whether to go remote, hybrid, or in-office. It tells them that the answer depends less on the policy and more on the systems behind it. The teams that build those systems outperform, regardless of where their people sit.
Related Reading
Written by
Kinetiq Team
Contributing writer at Kinetiq, covering topics in cybersecurity, compliance, and professional development.
