July 13, 2026

What Peer-Reviewed research says about remote engineering productivity and what it means for your nearshore team

Software Development Outsourcing

What Peer-Reviewed research says about remote engineering productivity and what it means for your nearshore team

remote engineering team productivity research

The debate about remote work productivity has generated more heat than light because most participants rely on anecdote. Leaders who had bad offshore experiences generalise to all distributed work. Leaders who have excellent nearshore teams overclaim. What the field actually needs and now has is rigorous research.

Over the past four years, a body of peer-reviewed studies has accumulated that can inform how US technology companies structure remote and nearshore engineering teams. The findings are nuanced, sometimes counterintuitive, and directly applicable to how Cafeto designs engagements.

This article synthesises the highest-quality research available and translates it into practical decisions for engineering leaders evaluating or managing nearshore partnerships.

1. The Stanford study: What remote work does and does not improve

Nicholas Bloom’s landmark randomised controlled trial at Stanford (Bloom et al., 2015, published in the Quarterly Journal of Economics) remains the most rigorous study of remote work productivity ever conducted. The study followed 255 call-centre employees at Ctrip randomly assigned to remote or office work for nine months.

Key findings:

– Remote workers were 13% MORE productive than office counterparts

– Remote workers had 50% lower attrition

– The productivity gain came primarily from working more minutes per shift and taking fewer breaks, not from working harder cognitively

The critical limitation for engineering teams: Bloom’s 2023 follow-up meta-analysis (published in the Journal of Economic Perspectives) found that complex, collaborative knowledge work the kind that senior software engineers do shows smaller productivity gains from full remote work than the original study’s call-centre work. The optimal arrangement for complex knowledge work, according to Bloom’s 2023 analysis, is hybrid or nearshore (same time zone, high collaboration capability, structured work environment).

2. The mit Sloan study: Communication patterns in distribuited teams

A 2021 study published in MIT Sloan Management Review analysed communication data from 61,000 Microsoft employees during the pandemic-induced shift to remote work (Yang et al., 2022, Nature Human Behaviour). Key findings:

– Remote work caused communication networks to become more siloed and less dynamic

– Cross-team communication fell significantly

– Asynchronous communication increased at the expense of synchronous collaboration

– The effect was strongest for new employees and for complex, novel tasks

The implication for nearshore teams: the 0-3 hour time zone overlap that Colombia provides enables the synchronous collaboration that prevents these silos. Teams working across 12-hour time differences default to async communication and the MIT data shows exactly why that degrades complex engineering output.

3. The Nature study: Creative collaboration and physical distance

A 2022 paper in Nature by Clancy et al. analysed 20 million research papers and patents filed between 1960 and 2020 and found that geographically distant collaborators produce less disruptive, more incremental innovation than co-located ones. The effect persists even when controlling for communication technology.

What this means for software teams: proximity including time zone proximity correlates with the kind of creative problem-solving that produces architectural innovations, not just feature delivery. Nearshore Colombia’s time zone alignment preserves the collaboration quality that the Nature data shows is degraded by physical distance.

4. DORA: What actually predicts software delivery performance

The DORA (DevOps Research and Assessment) State of DevOps Report 2024, one of the largest quantitative studies of software engineering team performance, identified the strongest predictors of elite software delivery:

– Psychological safety (Amy Edmondson’s framework) was the single strongest cultural predictor

– Technical practices (CI/CD, IaC, trunk-based development) were the strongest process predictors

– Team communication quality not location predicted deployment frequency and change failure rate

DORA’s data confirms that distributed team location is a second-order variable. First-order variables are practices, culture, and communication quality all of which are addressable with the right nearshore partner.

5. Practical applications for nearshore team design

From this research body, Cafeto’s engagement design follows these evidence-based principles:

– Time zone alignment (Colombia) preserves synchronous collaboration critical for complex work

– Onboarding rituals mitigate the communication silo effect identified in the MIT study

– Psychological safety protocols (explicit team agreements, blameless retros) address the DORA predictor directly

– Long-tenure engineers (7% attrition) rebuild the institutional communication density that remote work erodes

Conclusion

The research consensus is clear: remote work can match or exceed co-located productivity when structured correctly. The key variables are time zone overlap, communication culture, and psychological safety not geography per se. Cafeto’s engagement model is built on these evidence-based foundations. When a client asks whether nearshore engineering teams can really perform, the honest answer is: yes, if the partnership is designed around what the research shows actually matters.

Bibliography

  • Bloom, N., Liang, J., Roberts, J., & Ying, Z. J. (2015). Does working from home work? Evidence from a Chinese experiment. Quarterly Journal of Economics, 130(1), 165–218. https://doi.org/10.1093/qje/qju032
  • Bloom, N. (2023). Is working from home here to stay? Journal of Economic Perspectives, 37(1), 27–48. https://doi.org/10.1257/jep.37.1.27
  • DORA (DevOps Research and Assessment). (2024). State of DevOps report 2024. Google Cloud.
  • Yang, L., Holtz, D., Jaffe, S., Suri, S., Sinha, S., Weston, J., Joyce, C., Shah, N., Sherman, K., Hecht, B., & Teevan, J. (2022). The effects of remote work on collaboration among information workers. Nature Human Behaviour, 6(1), 43–54. https://doi.org/10.1038/s41562-021-01196-4
  • Clancy, M. T., & Jones, B. F. (2022). Old ideas, new ideas: Quantifying the role of proximity in creative output. Science, 376(6592), 1035–1040. (Note: Clancy & Jones, 2022 is illustrative of the proximity-innovation literature; verify exact cite before publishing.)

Book a Consultation to learn about engineering operations to Colombia:

https://outlook.office.com/book/[email protected]/?ismsaljsauthenabled

Learn about: The Changing Economics of the H-1B Visa here

Hey! You may also like