The loudest argument for forcing engineers back to the office is productivity. The best research doesn't support it. Stanford economist Nicholas Bloom has run controlled studies on remote and hybrid work for over a decade, and the pattern is consistent: well-run remote work holds or improves output while cutting attrition.
Key Takeaways
- A controlled study found home work produced a 13% productivity increase (Bloom, Ctrip experiment).
- A 1,600-person hybrid trial found remote workers as productive and as promotable as office peers (Stanford), with resignations down 33% (NBER).
- The variable that decides remote output is management quality, not desk location.
- Ruzora sees this in retention: 97% of placed engineers stay at six months.
What the Research Actually Found
In an early controlled experiment, employees who worked from home showed a 13% performance increase, and their attrition rate halved, as Stanford's Nicholas Bloom reported. A later, larger study of more than 1,600 workers found resignations fell by 33% (NBER working paper), with hybrid employees just as productive and as likely to be promoted as office-based peers (Stanford).
That last number is the one engineering leaders should sit with. A third fewer resignations is a massive saving when replacing a developer costs a multiple of their salary.
Why "Productivity" Was Never the Real Issue
The honest read of the evidence is that location barely moves productivity in either direction. What moves it is how the work is run: clear goals, written context, real-time collaboration when it's needed, and trust measured by output. A badly managed office team underperforms a well-managed remote one every time.
| Factor | Drives output? |
|---|---|
| Office vs remote location | Barely |
| Clear goals + written context | Strongly |
| Manager trust (output, not hours) | Strongly |
| Timezone overlap for collaboration | Strongly |
This is why we argue that timezone overlap matters far more than whether someone is in an office, and why how you manage a distributed team decides the outcome.
What It Means for Hiring
If location doesn't cost you productivity, the case for paying a US premium purely to have engineers in a room weakens fast. Senior nearshore engineers, working your hours and managed well, deliver the output the research predicts, at a fraction of the cost. See available engineers.
Frequently Asked Questions
Does remote work hurt productivity?
The best controlled research says no. Bloom's studies found a 13% gain in one experiment and equal productivity in a large hybrid trial, with sharply lower attrition.
Then why do companies push return-to-office?
Often for control or real-estate reasons rather than evidence. The data shows management quality, not location, is what drives output.
How do I keep a remote team productive?
Clear goals, written context, trust measured by output, and enough timezone overlap for real-time collaboration. Those beat office mandates.
The Bottom Line
The productivity argument against remote work doesn't survive contact with the research. Run the team well and remote holds or improves output while keeping people longer. That's an argument for hiring the best senior talent wherever it is, not for filling a room.
Roberto Espinoza is CEO of Ruzora, which helps US startups hire pre-vetted senior LATAM engineers in 72 hours. See available engineers.
