Microsoft Study Finds: Remote Work Enhances Developer Productivity
Remote work has been an ongoing trend in numerous industries, and a recent study conducted by Microsoft confirms its positive impact on developer productivity. The study, led by Brian Houck, principal productivity engineer at Microsoft, analyzed the productivity patterns of 5,000 developers within the company and revealed some intriguing findings.
Amid the COVID-19 pandemic, Microsoft, like many other companies, transitioned to a fully remote work environment. This presented Houck and his team with the opportunity to investigate the effects of remote work on developer productivity. Surprisingly, their research indicated that developers were not only more productive when working remotely, but they also reported higher job satisfaction compared to when they were in the office. It’s worth noting that a hybrid work arrangement did not yield the same productivity benefits or job satisfaction.
The study highlighted that developers lose focus due to distractions such as waiting for code reviews and attending meetings. Focused work was identified as a crucial factor contributing to productivity, while distractions hindered it significantly. The researchers discovered that measuring productivity was a complex task. Although the number of developer pull requests increased by 20% during the full remote work period in the spring of 2020, the developers were feeling miserable, working long hours and feeling disconnected from their teams. This finding suggests that productivity cannot be assessed solely based on output quantity.
The study also emphasized that productivity and job satisfaction varied based on different circumstances. For instance, 55% of developers reported fewer distractions while working remotely, while 49% experienced more distractions. According to Houck, productivity encompasses various aspects, such as how happy and fulfilled developers feel. Developers mentioned factors such as acquiring knowledge, achieving business outcomes, and the volume of work as indicators of productivity.
Furthermore, the research team concluded that developers derive happiness and job satisfaction from spending their time coding rather than engaging in non-coding tasks like reading and writing emails. The time spent coding also appeared to correlate with overall job satisfaction. Interestingly, the number of lines of code written or bugs fixed did not influence how productive developers felt on a given day.
The study shed light on another challenge faced by developers—the struggle to separate work and personal life. The researchers found that this boundary struggle had a significant impact on self-reported productivity. To address this issue and promote focused work, developers were advised to formally block time on their calendars dedicated to coding. The study revealed that developers who did this were able to accomplish 80% more coding during these dedicated periods compared to vacant blocks of time on their calendars. Setting aside specific periods proved more effective than trying to find free moments throughout the day.
In order to optimize focused work, the researchers also recommended reducing the number of low-quality meetings. Many developers cited excessive meetings as the second-most significant workplace challenge. Identifying low-quality meetings was relatively simple—developers should refrain from multitasking during these sessions. If developers find themselves sending emails or coding during a meeting, it indicates that the meeting may not be beneficial to their productivity and focus.
Microsoft’s study provides valuable insights into the productivity patterns of developers in a remote work environment. It highlights the importance of focused work and the impact of distractions. Furthermore, it emphasizes the need to prioritize developers’ happiness and job satisfaction by enabling them to spend more time coding and reducing low-quality meetings. By implementing these recommendations, organizations can enhance their developers’ productivity levels and overall job satisfaction.
