Somewhere around 2020, we collectively decided that remote workers are more productive than in-office workers. You've seen the studies. You've probably cited them. Some of them are real. Most of them measure the wrong thing.
Here's the uncomfortable version: remote work doesn't automatically make people more productive. It changes what productivity looks like, where it happens, and who benefits. That's actually a more interesting story — but it requires admitting the blanket claim is too simple.
What those productivity studies actually measured
The landmark studies from 2020 to 2022 mostly measured call center workers and customer service roles. People in jobs where output is easy to count: calls handled per hour, tickets closed, units processed. In those studies, remote workers did perform better — fewer interruptions, no commute drain, quieter environment.
That's real. But most knowledge workers don't have jobs that look like that. A product manager's output for the week isn't measurable in units. Neither is a designer's. The "output" of a good engineering week might be one decision that saves six months of rework — not lines of code.
When you measure knowledge work productivity by lines of code or tickets closed or hours logged, you're measuring the wrong thing. And remote work, if anything, makes it easier to generate the visible signals of productivity without doing the work that actually matters.
The hidden cost that doesn't show up in studies
Ask any engineering manager at a company that went fully remote what the hardest part has been. The answer almost never involves whether people are working enough hours. It's about knowledge transfer. The informal conversations that no longer happen. The junior engineer who used to absorb context by sitting near senior people. The moment in the office kitchen where someone mentioned a problem and someone else happened to know the answer.
That ambient knowledge flow is almost impossible to study, so it doesn't show up in the productivity research. But it's real, and its absence has cost a lot of teams a lot of time.
None of this means remote work is bad. It means the challenge of remote work is not "are people slacking off?" It's "how do we create the conditions where knowledge moves and people grow without a shared physical space?"
Who remote work is actually harder for
Early-career people got the worst of the remote transition and nobody talks about it much. The first two or three years of someone's career are almost entirely about learning by proximity. Watching how a senior person handles a client call. Getting feedback in the hallway. Absorbing how decisions get made before you're the one making them.
Remote work strips most of that out. You get the task but not the texture around it. You can execute but you miss the context about why things are done a certain way. That gap compounds. By year three of a fully remote job, some people have significantly less institutional knowledge than they would have had in person — and they don't necessarily know it.
Managers who were already senior when the shift happened mostly did fine. They had the context. They had the relationships. They knew how to operate. The people who got shortchanged are the ones who were supposed to build all of that during the years they were working from their apartments.
The productivity that remote work actually unlocks
Here's the real case for remote work, and it's better than "people work harder at home." Remote work allows teams to hire the right person for a job regardless of geography. It removes the commute, which for many people was a two-hour daily tax on their lives. It gives people control over their environment, which matters enormously for how well someone thinks. And for certain kinds of focused work, the absence of an open office is genuinely a gift.
These are real advantages. They're just different advantages than "output per hour goes up."
The companies that thrive with remote teams aren't the ones who assumed productivity would magically improve. They're the ones who built explicit systems to replace what the office provided informally: structured knowledge sharing, intentional onboarding, documentation practices that capture context, and yes, async tools that move information without requiring everyone to be available at the same moment.
The question worth asking
Instead of "are remote workers more productive?" the question that actually produces useful answers is: "what does our team specifically need to do good work, and how do we make sure that happens regardless of where people are?"
Sometimes that means async video updates to replace status meetings. Sometimes it means rigorous documentation. Sometimes it means one well-designed in-person gathering per year that you invest in properly. It's never just a blanket policy.
The myth worth debunking isn't that remote work is bad. It's that it's a free upgrade. It's a different way of working that requires deliberate design. Teams that treat it that way tend to do well. Teams that just sent everyone home and hoped for the best have had a rougher time.