Why the Remote-Work Debate Stays So Heated
theatlantic.com
theatlantic.com
You've got workers that want to work from home. You have workers that really don't want to work from home.
Then you've also got antiworkers that want to "work" from home. And antiworkers that want to "work" from the office and get facetime so they can still make career progress.
And then you've got facilities management people that need to justify office space. What happens if they don't? Do they still have jobs if a lot of offices get cancelled?
Then you've got sales types who need an office for occasional client meetings. And corporate politics makes that hard if they can't justify it by having the few local workers show up regularly.
I've probably left out many ulterior motives, because there are plenty. Any time there are plenty of unspoken motives, things get heated easily.
And a company who has to support remote and non remote kinda have an issue since they now have to know how to work both ways.
I worked at Dropbox for a couple of years post-remote-work, and I think they got this bit right: They kept a substantial amount of office space, kept on-site cafes, and turned those office spaces into collaboration spaces. You aren't supposed to (officially, "allowed to") use them for solo work. But, team off-sites are now on-sites, so there's always a smattering of people in the office, and there's plenty of space for sales to have client meetings as necessary, too. And, despite the requirements not to, I know there are people who go in just for some coworking at times.
There obviously is an advantage to in-person collaboration. There obviously is an advantage to building relationships with co-workers. There obviously is an advantage to letting a junior hire shadow you in person.
There obviously is an advantage of being able to confirm that someone's ass is in a seat and that there's a padlock on the door that doesn't open until the end of shift and that you can make all employees put their iPhone in a box to guarantee that it won't distract them while they work and to ban headphones.
I think the question is: is it worth letting companies have that level of control over employees?
I'm reminded of the first software job I had out of uni where I started doing push-ups and sit-ups in a spare room of the building. I got a few other software guys to join me. We'd do 100 push-ups and then get back to work, fired up. You couldn't see into the room. People just know we went there a couple times a day for 10 minutes.
Well, someone decided that they didn't like us doing that and they told us to stop even though it was no more disruptive to anyone than going to grab a coffee from the break room.
At 21 years old I remember being incredibly resentful that I didn't even have that level of control over my life just because I was someone's employee. Even though I was just trying to stay awake and get fired back up to do some work.
And I chuckle about it now when I do a full body workout in my apartment while waiting for pointless Zoom meetings to conclude.
I know that’s not the case everywhere and it seems bizarre. If you’re not hiring people who want to be productive, everything else is just deck chairs. And if you are hiring productive people, it’s insane to set global policies that limit their ability to optimize?
It all seems like arguing which breed of horse is better for the carriage.
That's a pretty big advantage too.
Is any of that “obvious”? It goes against everything I’ve seen in my career. The least productive people are those that “build relationships” in the office. The most productive are those who crank out code from home with little to no fuss. I’ve also seen juniors excel remotely because they have the space to research whatever they need and in a remote environment, often feel more comfortable reaching out to senior people for help than the would irl.
0 - https://www.forbes.com/sites/bryanrobinson/2022/02/04/3-new-...
My productivity tanked completely ever since we were forced back to the office. It almost burned me out.
Based on my own personal experience, good companies want to be accommodating because they understand people truly are the most important resource. They strive for a good balance of company-vs-employee desires. Who knows, maybe I am just lucky; maybe my past 30yrs working for big-tech is an anomaly?
Doesn't exist.
Like the studies show, people are as productive at home as at the office. Going to the office doesn't change effort. You're also implying that one can't improve while working from home, which isn't true.
Or, how about employees who believe what reddit tells them: they are being mistreated/abused because they can't have it their way?
I don't know what you're talking about specifically, but at a minimum, considering wages for workers are stagnant for decades while executive pay is (way) up, it's easy to see how workers are being exploited by default.
The likelihood of observing new things (except maybe new traffic jams or train delays) on your daily commute is pretty low, I would say - and (how convenient!) increases if you only do the commute, say, once per week. And, of course, will only happen if you don't spend all of it with your eyes glued to your phone...
Meanwhile, those who live in shoeboxes need the external space to stay sane.
Don't underestimate the selfish reasons on either side.
My point is choosing either on-site or WFH means someone has gotten a bad deal. Personally I think the environmental argument trumps most others.
I really think it's poor logic to think one is better than the other: There are tangible advantages to both; and both work better or worse depending on the needs of the job and the kind of team that the company builds.
When I worked at Intel, they had to cut back on telecommuting because people were really abusing it. Yahoo did the same. On the other hand, telecommuting and hybrid worked very well for me for almost a decade. My wife and I would find being a two-career couple, with children, much more difficult if I had to be in the office five days a week.
I will point something out: If you need to telecommute to be productive; that indicates poor management within your company. Management should help create an in-office space and time to focus; if they can't do that in office, they aren't managing. One approach is "only take meetings by appointment." Another approach is team-wide dedicated focus time.
Don't be Tesla.
So many people make it out to be remote v office and hybrid is the devil. I'm adamant that people want the flexibility to work how they see fit for the job at hand. Unfortunately, this doesn't typically align with all the other people in their division/team. Some will want to socialise in the office while others have commitments at home, some will want the focus they can only get in the office, while others want the focus they can only get at home. So you have a stalemate (or a planning problem).
I think Nick's right, in 10 years time it'll be a lot less controversial, there will be companies who are mainly remote, some who are main onsite and others that are both.
...and the groups of people who own office buildings who must be starting to sweat.
People will scream online because they don't want to have to actually talk to the people in their company making the decisions, because they know by the time that happens it's already been decided.
* formal onboarding guide checked in with the code. New people should be fixing errors and pushing patches to it as they go. The guide should cover all the logins and services, dev process, how to build and run the product, etc.
* frequent 1:1 from boss and tech leads the first month
* online social event to meet the team, bs, maybe play a game
* automation in ci to build and test product for anyone to hit the button
* maintain curated culture for faqs, problems, shared scripty bits. wiki, private SO, shared repos, etc
* maintain SOP documents for common operations like making a releaseThere is a timecode assigned for this, so the buddy isn't making time around other things; that day, this is a main part of their job.
On the first day, the principal task is a full clone and build of the principal software the new starter is working on. The second day is going through a full process of ticket assignment, working it, completing it (ticket carefully selected to be possible in a day and to exercise full process, so buddy has to introduce them to testers etc). And so on. Each day, a new face, a new buddy, and pretty soon they've met everyone on the team and had useful interaction completing real tasks.
It’s been labeled in the past an intentional effort to sell cars, gas, and take people out of their communities as social control over time and agency.
I think given all the ways the people of the recent past have been shown wrong, we do not owe doing as they expect by default. It’s not as if they’re capable of putting up much fight at this point.