I. Introduction
Working from home (WFH) has been rising for years, as more occupations use computers and telecommunications, more people have reliable home internet connections, and more families have both parents working full time. The COVID-19 pandemic accelerated this process by forcing a large fraction of the global workforce to switch to WFH at least temporarily. Even if only a fraction of this shift became permanent, it would have implications for urban design, infrastructure development, and reallocation of investment from inner cities to residential areas. It would also have significant implications for how businesses organize and manage their workforces. However, little is yet known about some of the more fundamental consequences of WFH, including its effects on employee productivity.
In this paper we provide a comprehensive analysis of the effect of WFH on employee productivity at HCL Technologies, a large information technology (IT) services company based in India. The company abruptly switched all employees from WFO to WFH in March 2020, in response to the largely unanticipated pandemic shock. Our study has several novel and interesting features.
Second, the firm provided unusually broad and high-quality data. Employee productivity for high-skilled jobs is notoriously hard to measure. The data include a quantitative measure of employee output, which the firm goes to significant lengths to calculate and uses to supervise and evaluate these high-skilled professionals. Employee time use was captured by monitoring applications on work devices, so we know total hours worked, start and end times, how much time was spent in various types of meetings and communications, and how much time the employee focused on work without interruptions. The high-quality performance measure and total work time provide a natural and relatively accurate measure of the employee’s productivity. These outcome measures are some of the best that modern analytics and monitoring software can provide. The firm also provided information on the types of meetings and communications in which employees engaged, providing valuable insights into how employees spent their work time in WFH compared to WFO. Finally, we know employee experience, age, gender, whether there are children at home, and the employee’s usual commute time.
Our key findings are as follows. Employees significantly increased average hours worked during WFH. Much of this came from starting work earlier and ending it later in the day. At the same time, there was a slight decline in output as measured by the employer’s primary performance measure. Combining these, we estimate that average employee output per hour of work declined by 8%–19%.
The increase in overall working hours and corresponding decrease in productivity are associated with substantial changes in working patterns during WFH. Employees spent more time participating in a larger number of shorter, larger group meetings, but less time in personal or small group meetings with their manager. They had less “focus time,” that is, work time uninterrupted by meetings or calls. At the same time, they narrowed the scope of their networks, engaging in fewer contacts with colleagues and organizational units inside and outside the firm. All of these factors were significantly correlated with changes in employee productivity. These findings are evidence that coordination and communication are more difficult with remote work.
We also uncover some interesting dimensions of heterogeneity. Employees with lower company tenure decreased output slightly more during WFH, whereas output remained about the same for those with longer tenure. This suggests that employees who are more adapted to firm culture and processes are better able to work remotely, where there is no colleague at the next desk for quick help or advice. As a separate effect, those with greater career experience increased hours worked during WFH more than those with lower experience, with no effect on productivity. This suggests that more senior employees, with greater managerial duties, spent more time coordinating during WFH.
Our evidence yields important insights into how to implement hybrid WFH/WFO work. Communication, coordination, and collaboration are more difficult in a virtual context. This challenge must be addressed to implement significant WFH in occupations where such considerations are important, especially for less experienced employees. While WFH will remain a feature of modern workplaces, some aspects of in-person interactions cannot easily be replicated virtually, including the quality of collaboration and coaching, client engagement, and “productive accidents” that arise from spontaneously meeting people (including those with whom there is not yet a working relationship).
II. Data and Empirical Strategy
The workforce is highly skilled and educated. Virtually all have at least a bachelor’s degree, often in a technology field such as computer engineering or electronics. Most work at the company’s large, modern corporate campuses in several Indian cities. These campuses look and feel very similar to what one sees at Microsoft, Apple, or Amazon. All authors have visited the company headquarters, and senior executives spent considerable time explaining practices and business conditions to us.
That employee goal setting is embedded in a corporate-wide process and tied to each supervisor’s own goals and evaluation is important. If managers lowered the goals of employees in their team, it would make fulfilling team goals harder, and is therefore not in their interest. Company executives confirmed that goals were not changed as a result of the pandemic or the switch to WFH. Indeed, most of the company’s customers are also information technology firms, and that sector performed well during the pandemic. This firm and its clients largely continued expected business activities.
These plans and goals form the basis of supervision. Informally, managers monitor employee work time and performance across key applications and tasks, in order to better supervise and coach them. This is supported by the analytics platforms described below. Formally, each employee is measured by performance against monthly goal on a key metric, which we will refer to as “Output.” He or she also receives quarterly supervisor feedback and biannual subjective performance ratings.
A notable advantage of this study is that the performance measure is relatively rigorous and objective, despite the fact that the employees are high-skilled professionals for which performance is notoriously hard to measure.
The supervisor devises the key metric to reflect the most important aspect of the job, and this is tracked with the analytics systems. For example, for a software engineer it might be the number of code segments completed. Importantly, the measure does not merely reflect quantity. It is Output conditional on adequate performance on other dimensions of the job, such as quality or client satisfaction. Code segments will not be counted as complete until they meet company and client standards for errors, speed, and functionality. Moreover, since the measure is output-based, it reflects various employee inputs, including time, effort, skill development, client interactions, drawing upon colleagues for advice, and so forth. Thus our measure is broader than might initially seem apparent, accounting for key intangible aspects of each employee’s performance.
The employees in our sample do not receive incentive pay tied directly to this or any other measure. Compensation is composed of salary, an annual merit bonus based on overall performance, and occasional small rewards for activities such as suggestion of valuable new ideas. That the performance measure is tied to the company’s business plan suggests employees are motivated to try to meet their goals, and our evidence confirms this. However, motivation is broader than this, due to supervisor monitoring, feedback, subjective evaluation, merit pay, and the potential to earn a promotion (as is true at most companies).
Company financial statements reveal that total workforce size and revenue both rose by more than 5% in 2020 compared to 2019, and profit margins rose even more. Promotion rates were higher in 2020 than in 2019. Thus employees did not experience any decline in formal or informal incentives during the sample period.
A. Main Outcome Variables
We obtained data for all employees from the R&D part of the firm who are managed via these systems. Data cover April 2019 through August 2020, resulting in a panel data set with 10,384 unique employees observed over 17 months. The company moved abruptly to WFH in March 2020 as COVID-19 became serious in India.
Sapience Analytics software is installed on employee work devices. It records the time that an employee is working by tracking applications or websites used, and whether the employee is active (i.e., using the keyboard or mouse). If an employee procrastinates on a social media platform, and this is not part of the job, that would not be recorded as work time. If a program from a predefined list of relevant tools (programming, collaboration, document production, communication, etc.) is active, that is recorded as work time. It includes meetings entered in the Outlook calendar, which is used throughout the company, even if these are face-to-face. Sapience therefore records effective work hours. If an employee sits at his or her desk for 8 hours a day, Sapience might only record 5 hours, because breaks or surfing the web are not effective work time. Employees are aware that the software is used in this way.
It is possible to complete more tasks than are assigned, so the outcome variable Output can take values in , but is typically between 0 and 100. The most common value is 100, meaning that employees continue working longer hours until they meet their targets, but we also see employees falling short of or exceeding their targets.
B. Employee/HR Variables

| Mean | Standard Deviation | 1st Quartile | 3rd Quartile | Observations | |
|---|---|---|---|---|---|
| Age (years) | 31.91 | 5.95 | 27.10 | 36.03 | 7,969 |
| HighAge | .50 | .50 | .00 | 1.00 | 7,969 |
| Tenure (years) | 4.21 | 3.90 | 1.11 | 5.11 | 7,969 |
| HighTenure | .52 | .50 | .00 | 1.00 | 7,969 |
| Experience (years) | 8.10 | 5.22 | 4.04 | 11.10 | 7,969 |
| HighExperience | .50 | .50 | .00 | 1.00 | 7,969 |
| Male | .76 | .43 | 1.00 | 1.00 | 7,969 |
| NumChildren | .52 | .73 | .00 | 1.00 | 8,934 |
| Children | .39 | .49 | .00 | 1.00 | 8,934 |
| CommuteTime | .65 | .33 | .38 | .85 | 4,323 |
| Rating | 2.66 | .88 | 2.00 | 3.00 | 5,354 |
Age, company tenure, and industry experience (collected at hiring and updated to the current date) are all measured in years. For each we generate median splits: HighAge, HighTenure, and HighExperience. Mean age is quite young, which is not unusual in the IT sector. Mean tenure is low at about 4 years, as is expected since employee turnover is high in the IT sector. As in tech companies around the world, men are a significant majority.
The variable NumChildren is the number of children up to age 21 who are covered under the company’s employee health insurance plan. The company believes that the vast majority of employees who have dependent children insure them via the company, because of its relatively generous health insurance coverage. However, some might instead be insured through a partner’s employer. Hence, a zero means that there are either no children at home, or there are but they have not been declared. The dummy Children equals 1 if and only if NumChildren is positive.
C. Workplace Analytics Data

| Mean | Standard Deviation | 1st Quartile | 3rd Quartile | Observations | |
|---|---|---|---|---|---|
| WFO (before March 15, 2020): | |||||
| Working Hours | 44.71 | 5.16 | 43 | 46.46 | 6,755 |
| After Hours | 9.64 | 9.55 | 2.33 | 14.04 | 6,755 |
| Focus Hours | 34.49 | 9.02 | 30 | 41.25 | 6,755 |
| Collaboration Hours | 10.20 | 9.24 | 3.55 | 13.75 | 6,755 |
| Meetings Manager | 3.97 | 4.35 | .5 | 5 | 6,755 |
| Meetings 1∶1 | .18 | 1.37 | 0 | .5 | 6,755 |
| Coaching Meets | .13 | 1.03 | 0 | 0 | 6,755 |
| MS Teams Calls | .36 | 1.63 | 0 | 0 | 6,755 |
| Internal NW | 18.91 | 14.21 | 10 | 24 | 6,755 |
| External NW | 2.58 | 3.61 | 0 | 3 | 6,755 |
| NW EXT | .98 | 1.04 | 0 | 1 | 6,755 |
| NW ORG | .05 | .22 | 0 | 1 | 6,755 |
| Emails | 23.61 | 23.68 | 9 | 30 | 6,755 |
| WFH (after March 15, 2020): | |||||
| Working Hours | 49.03 | 7.58 | 45.14 | 52.49 | 19,220 |
| After Hours | 12.98 | 12.70 | 3.71 | 18.44 | 19,220 |
| Focus Hours | 32.73 | 9.99 | 28 | 40 | 19,220 |
| Collaboration Hours | 11.07 | 9.97 | 4.08 | 15 | 19,220 |
| Meetings Manager | 5.48 | 6.57 | 1 | 7.33 | 19,220 |
| Meetings 1∶1 | .11 | 1.07 | 0 | 0 | 19,220 |
| Coaching Meets | .09 | .98 | 0 | 0 | 19,220 |
| MS Teams Calls | 21.46 | 25.22 | 3 | 30 | 19,220 |
| Internal NW | 23.44 | 19.89 | 11 | 30 | 19,220 |
| External NW | 3.05 | 4.36 | 0 | 4 | 19,220 |
| NW EXT | .91 | .89 | 0 | 1 | 19,220 |
| NW ORG | .05 | .23 | 0 | 0 | 19,220 |
| Emails | 25.26 | 29.89 | 8 | 30 | 19,220 |
Note.
“Working Hours” are weekly hours worked. “After Hours” are weekly hours worked outside regular work time. “Focus Hours” are hours with 2 or more hour blocks not spent in meetings, on calls, or writing emails. “Collaboration Hours” are hours spent in meetings or MS Teams calls. “Meetings Manager” is the number of meetings involving the employee’s manager. “Meetings 1∶1” is the number of meetings between the employee and his or her manager. “Coaching Meets” is the number of meetings the employee attended with the manager and all of the manager’s direct reports. “MS Teams Calls” is the number of calls in which the employee participated. “Internal NW” is the number of people inside the company with whom the employee had meaningful contact in the last 28 days. “External NW” is the same measure for people outside the company. “NW ORG” is the number of distinct company organizational units (outside his or her own) with which the employee had at least two meaningful interactions in the last 4 weeks. “NW EXT” is the same measure for domains outside the company. “Emails” is the weekly number of emails sent by the employee.
Variables fall into several categories. Working Hours measures overall time worked by the employee. It is best viewed as capturing time “at work” (at home or in the office), not every minute of which is necessarily spent working; for example, it will count small breaks in between emails as work time. It can detect longer work hours due to additional email traffic, meetings in the calendar or online, and other activity involving Microsoft services. In contrast, Sapience Input captures time “effectively working,” excluding breaks or nonwork activities.
A second group of variables (Focus Hours, Collaboration Hours, Meetings Manager, Meetings 1∶1, Coaching Meets, and MS Teams Calls) relate to meetings. Focus Hours measures time blocks of 2 hours or more that are uninterrupted by meetings, calls, or emails. It is thus a measure of the amount of time the employee can concentrate on tasks. Collaboration Hours is the total time spent in various forms of meetings. The latter four variables measure time in meetings by structure and purpose. Meetings Manager is the number of meetings the employee attends that involve their manager, and Meetings 1∶1 are personal meetings between the employee and manager. Coaching Meets is the number of meetings involving the employee, his or her manager, and the manager’s direct reports. MS Teams Calls is the number of calls using MS Teams (which hosts video meetings similar to Zoom or Skype).
D. Empirical Strategy
where αi is the employee fixed effect, WFH is a dummy variable indicating months working from home, and CustomerTeamjit is a dummy variable equal to 1 if and only if employee i in month t was part of team j. Monthst is a month (not month-year) dummy variable, so that if and only if t is January, if and only if t is February, and so forth. In addition, we report an alternative specification controlling for a linear rather than seasonal time trend:
Once the average WFH effect is established, we analyze variation in this effect. Section III.B studies how effects vary with employee characteristics. We interact the WFH dummy in the previous specifications with additional explanatory variables X1i, X2i, … . Because the Xji variables are employee specific but time invariant, we do not separately control for them, as that is already achieved by the employee fixed effects.7
III. Results
A. Average WFH Effect

To quantify the WFH effect, and to control for employee and team time-invariant variables (via employee and team fixed effects), we now turn to the regression analyses. Informally, the estimates give us average differences in outcomes before and during WFH for the same employee, controlling for team effects (since employees sometimes switch teams) and time trends.

| Dependent Variable | ||||||||
|---|---|---|---|---|---|---|---|---|
| Input | Output | Productivity | LogProd | |||||
| (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | |
| WFH | 2.117*** | 1.592*** | −.530*** | −.098 | −.256*** | −.138 | −.334*** | −.288*** |
| (.034) | (.038) | (.125) | (.155) | (.031) | (.074) | (.008) | (.009) | |
| Linear month trend | .040*** | −.035* | −.010 | −.004*** | ||||
| (.003) | (.015) | (.007) | (.001) | |||||
| Employee fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Month fixed effects | Yes | No | Yes | No | Yes | No | Yes | No |
| R2 | .24 | .22 | .02 | .02 | .01 | .01 | .12 | .11 |
| Observations | 70,249 | 70,249 | 70,249 | 70,249 | 70,249 | 70,249 | 70,239 | 70,239 |
| Clusters | 10,312 | 10,312 | 10,312 | 10,312 | 10,312 | 10,312 | 10,312 | 10,312 |
Note.
Input is the individual time in hours that the employee worked per working day in a month. Output is the normalized output of the employee relative to the target in a month. Productivity is output divided by time worked. LogProd is the natural logarithm of Productivity. The unit of observation is the employee-month. Standard errors are shown in parentheses below the point estimates and are clustered on employee level.
*
Significant at the 5% level.
***
Significant at the 0.1% level.
Columns 7 and 8 explain the log of Productivity, which strongly increases the fit of the regression. The WFH effect is negative and significantly different from zero at all significance levels, irrespective of time controls.
In summary, this evidence indicates that employees worked longer but less productively, with output remaining about the same or dropping slightly. Our interpretation of these patterns is that employees were less productive during WFH, but still aimed to reach the same output or goals, and hence worked longer until the same output was reached. In the next sections, additional results will suggest that productivity decreased due to increased distractions and coordination costs.
If employees used their own devices to work from home, we would not track that activity (in either period). However, HCL did not allow employees to do so, to insure integrity of confidential client information. Any employees who worked at home in both periods had to use a company-owned laptop computer and phone, both of which included the tracking software used to collect our variables, with one small exception. During the transition to WFH, a small percentage of employees who did not yet have a company-owned laptop computer were briefly allowed to use personal devices to perform some work. This lasted only until the company could provide them with laptops. In such cases Sapience would not track their work, so our Input variable has missing values. This affects a very small percentage of our data.
B. Who Copes Better with WFH? Heterogeneous WFH Effects

| Dependent Variable | ||||||
|---|---|---|---|---|---|---|
| Input | Output | Productivity | ||||
| (1) | (2) | (3) | (4) | (5) | (6) | |
| WFH | 1.416*** | 1.599*** | −.528*** | −1.176*** | −.206*** | −.361*** |
| (.046) | (.086) | (.150) | (.267) | (.042) | (.075) | |
| WFH × Children | .307*** | .091 | .061 | .673 | −.169** | −.027 |
| (.059) | (.128) | (.205) | (.431) | (.058) | (.111) | |
| WFH × MaleWFH × Male | −.211* | .895** | .149 | |||
| (.094) | (.300) | (.093) | ||||
| WFH × Male × Children | .252 | −.822 | −.157 | |||
| (.145) | (.495) | (.133) | ||||
| Employee fixed effects | Yes | Yes | Yes | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes | Yes | Yes | Yes |
| Month fixed effects | No | No | Yes | Yes | Yes | Yes |
| Linear month trend | Yes | Yes | No | No | No | No |
| R2 | .23 | .25 | .02 | .02 | .01 | .01 |
| Observations | 64,392 | 58,644 | 64,392 | 58,644 | 64,392 | 58,644 |
| Clusters | 8,865 | 7,911 | 8,865 | 7,911 | 8,865 | 7,911 |
Note.
Input is the individual time in hours that the employee worked per working day in a month. Output is the normalized output of the employee relative to the target in a month. Productivity is output divided by time worked. The unit of observation is the employee-month. Standard errors are shown in parentheses below the point estimates and are clustered on employee level.
*
Significant at the 5% level.
**
Significant at the 1% level.
***
Significant at the 0.1% level.
In India, all schools closed in March 2020 during the COVID-19 pandemic, so working from home was presumably an even greater challenge for some parents, as children needed to be supervised and perhaps taught. Hence, we investigate whether having children at home changed an employee’s WFH effect. An important qualification is that under normal conditions, children would attend school and adverse effects of WFH on productivity of parents might be lower.
Column 1 shows that employees who have at least one child at home (as measured by company health insurance coverage) increased work time more during WFH than did their counterparts without children. Possibly, this is due to the fact that employees with children get distracted more often during WFH and compensate by working longer hours. Employees with children at home work almost a third of an hour more per working day during WFH than those without children, who themselves still work 1.4 hours more during WFH. These effects are highly significant. Column 3 reveals no significant change in the WFH effect on output with children at home. However, column 5 shows that the increased working time implies a larger drop in productivity when there are children at home. Consequently, the patterns seen for the average employee are exacerbated for employees with children.
The WFH × Male interaction represents the difference in the WFH effect between male and female employees without children. Male employees without children increased working time by about 0.2 hours less per day than did female employees without children, a significant effect at the 5% level. They also suffered a significantly smaller decline in output.
The WFH × Children interaction represents the difference in the WFH effect between female employees with and without children. Female employees with children did not significantly increase working time during WFH compared to female employees without children, nor did their output or productivity significantly differ.
Finally, the sum of WFH × Male and WFH × Male × Children is the difference in the WFH effect between male and female employees with children. This difference is roughly zero for all outcome measures, so there is no gender difference among employees with children at home.

| Dependent Variable | ||||||
|---|---|---|---|---|---|---|
| Input | Output | Productivity | ||||
| (1) | (2) | (3) | (4) | (5) | (6) | |
| WFH | 1.361*** | 1.516*** | −.743*** | −.603 | −.245*** | −.286*** |
| (.058) | (.095) | (.194) | (.334) | (.048) | (.083) | |
| WFH × HighTenure | .036 | .519* | .003 | |||
| (.067) | (.229) | (.090) | ||||
| WFH × HighAge | .057 | .097 | −.084 | |||
| (.092) | (.366) | (.073) | ||||
| WFH × HighExperience | .270** | −.138 | −.038 | |||
| (.094) | (.390) | (.084) | ||||
| WFH × CommuteTime | .107 | .316 | −.030 | |||
| (.122) | (.405) | (.093) | ||||
| Employee fixed effects | Yes | Yes | Yes | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes | Yes | Yes | Yes |
| Month fixed effects | No | No | Yes | Yes | Yes | Yes |
| Linear month trend | Yes | Yes | No | No | No | No |
| R2 | .25 | .26 | .02 | .03 | .01 | .01 |
| Observations | 58,644 | 31,848 | 58,644 | 31,848 | 58,644 | 31,848 |
| Clusters | 7,911 | 4,295 | 7,911 | 4,295 | 7,911 | 4,295 |
Note.
Input is the individual time in hours that the employee worked per working day in a month. Output is the normalized output of the employee relative to the target in a month. Productivity is output divided by time worked. The unit of observation is the employee-month. Standard errors are shown in parentheses below the point estimates and are clustered on employee level.
*
Significant at the 5% level.
**
Significant at the 1% level.
***
Significant at the 0.1% level.
The change in Output during WFH is roughly 0.5 percentage points larger per hour for employees with longer company tenure, holding age and experience constant. Thus, while low-tenure employees’ Output falls, high-tenure employees keep meeting their goals. The other characteristics do not show a significant effect. It appears that employees who had worked at the company for longer were able to adapt more effectively to the WFH shock, and that this was more important than general industry experience. This finding suggests that greater firm-specific human capital in the form of familiarity with company procedures, or more fully developed networks and working relationships with colleagues and clients, were helpful during WFH. Alternatively, those with greater experience or tenure might be in positions with more responsibility, and so responded more to the shift to WFH. For the last outcome measure, Productivity, there is no significant difference in the WFH effect among these employee groups.

For 43 teams the negative effect is statistically significant. Five teams, by contrast, show a statistically significant positive effect on productivity. With the exception of one team, those are all teams in the bottom half of the size distribution. In smaller teams it might be easier to solve coordination problems during WFH. Still, even among the smaller teams, the effect on productivity is negative for the vast majority.
C. Mechanisms: What Contributes to Lower Productivity?
1. Working Hours


| Working Hours | After Hours | Focus Hours | Collaboration Hours | |||||
|---|---|---|---|---|---|---|---|---|
| (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | |
| WFH | 4.431*** | 2.743*** | 4.212*** | 1.822*** | −2.665*** | −1.417*** | 1.251*** | .704*** |
| (.161) | (.218) | (.288) | (.320) | (.245) | (.297) | (.122) | (.137) | |
| Linear weekly trend | .096*** | .137*** | −.071*** | .031*** | ||||
| (.009) | (.014) | (.012) | (.005) | |||||
| Employee fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| R2 | .703 | .709 | .743 | .747 | .717 | .719 | .745 | .746 |
| Observations | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 |
| Clusters | 914 | 914 | 914 | 914 | 914 | 914 | 914 | 914 |
Note.
“Working Hours” are weekly hours worked. “After Hours” are weekly hours worked outside regular work time. “Focus Hours” are hours with 2 or more hour blocks not spent in meetings, on calls, or writing emails. “Collaboration Hours” are hours spent in meetings or in calls. The unit of observation is the employee-week. Standard errors are shown in parentheses below the point estimates and are clustered at the employee level.
***
Significant at the 0.1% level.
2. Networking and Collaboration
We now focus on networking and collaboration patterns in more detail. Understanding changes in networking and collaboration can tell us something about the value of additional time spent in meetings. Shifts in networking patterns can also impact productivity in different ways, for example, by affecting the exchange of knowledge and ideas.

| Internal NW | External NW | NW ORG | NW EXT | Meetings Manager | Meetings 1∶1 | Coaching Meets | Emails | |
|---|---|---|---|---|---|---|---|---|
| (1) | (2) | (3) | (4) | (5) | (6) | (7) | (8) | |
| WFH | −7.621*** | −.532*** | −.009 | −.150*** | 1.723*** | −.089 | −.060 | 4.282*** |
| (.369) | (.103) | (.005) | (.027) | (.205) | (.048) | (.033) | (.680) | |
| Linear weekly trend | .787*** | .078*** | .001** | .008*** | .016* | .002 | .002 | −.020 |
| (.026) | (.006) | (.000) | (.001) | (.008) | (.002) | (.002) | (.029) | |
| Employee fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| R2 | .801 | .758 | .665 | .624 | .757 | .320 | .386 | .766 |
| Observations | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 | 25,893 |
| Clusters | 914 | 914 | 914 | 914 | 914 | 914 | 914 | 914 |
Note.
“Internal NW” is the number of people inside the company with whom the employee had meaningful contact in the last 28 days. “External NW” is the same measure for contacts outside the company. “NW ORG” is the number of distinct organizational units within the company with whom the employee had at least two meaningful interactions in the last 4 weeks. “NW EXT” is the same measure for domains outside the company. “Meetings Manager” is the number of meetings involving the manager. “Meetings 1∶1” is the number of meetings between the employee and his or her manager. “Coaching Meets” is the number of meetings by the manager with all direct reports including the employee. “Emails” is the number of emails sent. The unit of observation is the employee-week. Standard errors are shown in parentheses below the point estimates and are clustered at the employee level.
*
Significant at the 5% level.
**
Significant at the 1% level.
***
Significant at the 0.1% level.
Columns 3 and 4 contain results for similar measures, focused on the number of organizational units inside and outside the company at which an employee interacted with someone (col. 4). Here we also see a decline in contacts caused by WFH, despite a general upward trend, though in the case of internal organizational units the decline is not statistically significant.
Columns 5–7 focus on collaboration patterns. In line with our earlier analysis, the number of meetings involving the manager increases. By contrast, the number of both one-to-one supervisor meetings and coaching meetings decrease during WFH. Employees seem to receive less mentoring and coaching, even though these effects are only statistically significant at the 10% level. Moreover, in WFH managers are spending more time managing groups rather than individuals.
Overall, these patterns highlight a detrimental impact of WFH on networking. Employees attend more meetings, which tended to involve larger groups, but have shorter duration. This reduces their focus time. Furthermore, they communicate with fewer individuals and organizational units inside and outside the company. They have fewer one-to-one meetings with superiors, and receive less coaching. The next section shows that these observations help explain why WFH lowered productivity.
3. Productivity
Last, we study productivity in this subsample. We first ask whether the drop in productivity from our main sample can also be found in this smaller WPA sample of employees.

| Sapience | WPA | ||
|---|---|---|---|
| (1) | (2) | (3) | |
| WFH | −.149* | −.056** | −.049* |
| (.072) | (.008) | (.020) | |
| Mean before WFH | 1.080 | .599 | .599 |
| (1.702) | (.531) | (.531) | |
| Employee fixed effects | Yes | Yes | Yes |
| Team fixed effects | Yes | Yes | Yes |
| Linear trend | No | No | Yes |
| R2 | .356 | .783 | .784 |
| Observations | 4,359 | 4,359 | 4,359 |
| Clusters | 888 | 888 | 888 |
Note.
Productivity is as in previous sections, Output divided by Sapience monthly work hours. Productivity WPA divides Output by the WPA Input measure “Working Hours” (aggregated to monthly level). The unit of observation is the employee-month. For 888 employees we have all three sources of information: Sapience, IDMS, and WPA. Standard errors are shown in parentheses below the point estimates and are clustered at the employee level.
*
Significant at the 5% level.
**
Significant at the 1% level.

| Before WFH | During WFH | |||
|---|---|---|---|---|
| LASSO | Elasticity | LASSO | Elasticity | |
| (1) | (2) | (3) | (4) | |
| Hours: | ||||
| Working Hours | Yes | .014*** | ||
| After Hours | ||||
| Meetings: | ||||
| Focus Hours | Yes | .033*** | Yes | .072*** |
| Collaboration Hours | ||||
| Meetings Manager | ||||
| Meetings 1∶1 | Yes | .002*** | ||
| Coaching 1∶1 | Yes | .003 | ||
| MS Teams Calls | ||||
| Networking: | ||||
| Internal NW | Yes | .040*** | ||
| External NW | Yes | −.000 | Yes | .029*** |
| NW EXT | Yes | .010* | Yes | .011** |
| NW ORG | Yes | .000 | Yes | −.001 |
| Emails | Yes | .053*** | ||
Note.
Adaptive LASSO linear regression results (“yes” indicates a variable was selected) and mean elasticity of productivity with respect to an increase of 1 percentage point in the variables selected by LASSO. Columns 1 and 2 show the results restricted to the period before WFH, and cols. 3 and 4 the results restricted to the period during WFH. For all variables in the table LASSO regressions include a dummy identifying weeks in which the variable is above average for a given employee.
*
Significant at the 5% level.
**
Significant at the 1% level.
***
Significant at the 0.1% level.
The variables selected by the LASSO include Working Hours, Focus Hours, and most networking variables. Working after hours and attending many meetings does not seem to contribute substantially to productivity, nor does spending time on MS Teams calls. The set of selected variables is quite consistent before and during WFH, with focus hours and the networking measures being crucial indicators of productivity. Interestingly, overall working hours is selected before WFH but not afterward.
In summary, in this section we showed that WFH induced a significant shift in working patterns. Employees worked more, including outside regular office hours, but had less uninterrupted time to focus on task completion as they spent more time in meetings. They networked less and spent less time being evaluated, trained, and coached. We further showed evidence that these reductions, especially in focus hours and networking, were detrimental to productivity.
IV. Conclusion
In this paper we have presented the most detailed analysis of WFH productivity changes for knowledge workers available to date. The paper makes a number of significant contributions. We study an occupation that is expected to be amenable to WFH, but involves significant cognitive, collaborative, and innovation tasks. The data provide an unusually high quality measure of employee productivity for knowledge workers. The breadth of the data allow for the first thorough analysis of determinants of WFH productivity. We provide evidence on how WFH productivity varies with employee characteristics, presence of children at home, and WFO commute time. We also use detailed data on how employees spend their work time to study the effects of job characteristics on WFH productivity. These latter results are important, since they provide insights into how the effectiveness of WFH may vary across different types of jobs, and thus key issues for firms to consider in deploying WFH.
Our main explanation for the decline in productivity is that some aspects of work are more difficult to perform in a virtual environment. We provide clear evidence that this is the case. Employees spent more total time attending more meetings of shorter duration. This reduced their focus time. Those meetings tended to involve larger groups. Less time was spent in direct interactions with the supervisor or close colleagues. Employees also narrowed their spheres of communication, interacting with fewer people and business units, both inside and outside the firm. Collectively these indicate that costs of communication, collaboration, and coordination are higher when done virtually.
Alternative explanations could be related to the stresses of the pandemic. However, the data show an immediate and persistent jump in work patterns and productivity at the shift to WFH, which is inconsistent with the gradual evolution of the pandemic. We found no evidence that employee work behavior varied with changes in lockdown restrictions in India. Employees actually had a decline in sick days. Finally, company economic performance was quite good during this period of time, and promotion rates rose, so career concerns were not an issue.
Another possible explanation is the presence of children at home, exacerbated by the closing of schools. Indeed, WFH productivity was lower for employees who had children at home, so this is a partial explanation. However, those without children at home also suffered a large decline in productivity, with similar patterns for reduced focus time, increased time spent in large meetings, and decreased one-to-one communications and meetings.
It is likely that WFH also resulted in a decline in intangibles that are valuable to the employee and the company. Working relationships, professional networks, and corporate culture may have suffered. More subtly, when people work in the same location, they experience unplanned interactions. That can lead to new working relationships and “productive accidents” that spur innovation. It is not easy to generate similar unplanned interactions on teleconferences. Finally, employees had fewer opportunities for coaching and for meeting directly with supervisors. This undoubtedly slowed their development of human capital.
HCL executives were not surprised by the findings in this paper, which accord with their perceptions of the experience with WFH. As of mid-2021, they estimated that perhaps half of their employees had moved from their original locations, primarily to live with extended family (there were still significant pandemic-related restrictions). According to one senior executive, “Bringing them back to our base locations will not be easy.” The company expects to make significant use of WFH in the future, with perhaps 30%–40% of employees in WFO on any given day. No doubt productivity will improve as the firm refines implementation of WFH and moves to a blended model with WFO. Moreover, employees will enjoy greater flexibility and lower commute times, which compensates to some extent for lower productivity.
The findings in this paper will be helpful well beyond this firm. We have presented evidence on some of the challenges of implementing WFH. In particular, WFH may be more difficult for employees who are less experienced, have lower tenure, and for jobs that involve significant communication, collaboration, and coordination. Firms will have to develop tools, training, and policies to give greater emphasis to interpersonal interactions during WFO, improve effectiveness of virtual communication, and train supervisors and employees to schedule work time at home more efficiently.
