The utility of work from home for the employer and employee varies considerably.
My story from the perspective of someone in devops with a distributed team working in a backoffice role…
Like most, my employer (an ISP) went WFH for all positions that did not require physical presence March 2020 through the end of 2022. Administrative offices were never fully shut but usage plummeted to near-zero with the few regulars being split between those whose jobs were tied to the facility, those without adequate home internet access for WFH, and a remainder who tired of being cooped up at home all the time or otherwise wanted that geographic bookened between home and work life.
The first ~2 weeks of adjustment were interesting. My team (IT) was already set up for WFH because of late-night change management (and sick days) so we had made the conceptual leap(s) already. Many of the rest had not and had to deal with the likes of kid/spouse/pet management, realizing that working from their couch wasn’t sustainable, that they had to be available via email/IM, etc. The VPN stumbled a few times. But we got through it.
Not everyone got WFH. As an ISP we have a large number of Installation & Maintenance people that have to be were the network is, including subscribers’ homes. Facilities maintenance, business support, datacenter folks had to be at their respective offices.
Early 2023 the administrative offices started being consolidated and reopened. Some found themselves without a nearby office to return to, others learned that their office was moving. I was in the latter case - the offices closer to our physical presence were closed while a swank new downtown office was opened. 2024 the hybrid model was replaced with 3-4 days in the office.
The new office is a former century-old warehouse - cool to look at for the first ~day, but the acoustics of working in literal concrete rooms grate. Add in the hellscape of hotdesk pack-in/pack-out for a workforce previously accustomed to cubes and it grates further. Also, the workforce was largely coalesced around the company’s presence so it’s an inconvenient drive for everyone.
For me - and most of the other orgs within the company I know - the workforce remains geographically distributed. My manager is on the east coast (with no local direct reports!), one co-worker moved to India, one is local, and two are on the west coast. The related team has a manager + one peer locally, and three on the west coast. And for all that’s great about collaboration, that’s handled by that corporate standard Teams calls; even when there are local people almost no one bothers with a conference room.
I’d rather go back to 2023’s hybrid model. Twice a month in the office is all that’s really necessary for sprint stop/start; once a week would keep faces familiar and also allow for collaboration days.
…
More generally, I can understand senior management’s need for working in-office. They spend the overwhelming majority of their day in meetings - be it in conference rooms, fancier telepresence than Teams, or informal deskside affairs. As one goes up the chain they also must work with incomplete information and being in-person with people who prepared the information to feel them out can prove critical to making high-level decisions.
But get outside of senior management and this need tends to fall off quickly. For starters, every minute of senior management meeting depends on many minutes - if not hours - of work performed by others lower down the hierarchy. And that work often needs to be focus work, best done in isolation. Even famously collaborative fields like marketing tend to be 75% individual focus work.
Other cases that come to mind…
- Onboarding : New hires definitely need the “tap on a shoulder” level of support from peers
- Team co-location : If the bulk of the team is all local to a given office, that potential level of beneficial collaboration jumps
- Major projects : Complex or significantly cross-functional work benefits from in-person collaboration