Remix.run Logo
tempest_ a day ago

This often just feels like bad management.

They go remote, but don't change a lot of other things or attempt to mitigate the downsides (there are downsides, everything is a trade off) and then claim its a failure when they need a stealth layoff.

Also IBM has a long history of "Resource Actions" so this type of thing is not all unexpected from them.

martinald a day ago | parent | next [-]

I don't know if it's bad management per se. I think some people are very well suited for remote; some people aren't. Probably a rough extension of introversion/extroversion in the people mix.

If you take a bunch of very extroverted people and have them all work remotely they will not have a good time (in general).

Equally; if you take a bunch of very introverted people and have them in an office they'll really not like it, especially in open plan.

The other problem is fraud levels in hiring for fully remote is absolutely shocking. There are so many stories now of fake candidates etc, massive cheating in interviews with AI, etc. I've seen many stories like that even with really 'in depth' interview processes, so much so people are now going back to in person interviews en masse.

My rough take is that organisations need to really rethink this home/office thing from first principles. I suspect most engineering teams can work as well/better fully remote. I very much doubt all roles are like that. I think we'll see WFH being based on department or role rather than these global policies.

acdha a day ago | parent | next [-]

I think both problems are real, and your last paragraph really gets at why. People and jobs vary widely, and so does the quality of management. If you have a strong business and reasonably mature teams, you might not even realize problems with your management culture and practice are until something big changes; conversely, if you have strong managers you might have been able to soak up a lot of personnel and job issues before they got attention because some unappreciated middle managers put a lid on potential problems first.

In all cases, you really someone with time to look at the business as a whole to evaluate these things. For example, one of the things which has made RTO unproductive for many workers are open plan offices, which is a really easy problem to see and fix if workplace productivity is someone’s job but not if the RTO push is being driven by politics or the need to justify leases.

martinald a day ago | parent [-]

Agreed, but falling commercial real estate prices will allow some forward thinking companies to go back to private offices for developers, which arguably is the best solution (apart from commute/flexibility) for most, productivity wise.

Shog9 a day ago | parent | prev | next [-]

Funny you mention fraud... I worked for a company for quite a while that was absolutely dedicated to WFH for engineering - but swore up and down that sales just couldn't work without "bullpen" office setups.

Come to find out at least one entire office was engaged in widespread misreporting and fabrication. Turns out fraud is pretty tempting when you can easily avoid any paper trail.

bcoates a day ago | parent | prev | next [-]

Re:introvert/extravert I suspect it's the reverse.

Extraverts, broadly, aren't afraid of picking up the phone and calling you to chat about the email they sent you three minutes ago while driving and also on mute in a zoom; introverts can use remote work to be unreachable in a way they can't if you can just walk over and impose yourself on them.

missedthecue a day ago | parent | prev | next [-]

yeah I feel like blaming management is like blaming teachers when students got bad scores during remote-schooling. You can give them all the resources they need to succeed, but if they'd rather go to the dog park in the middle of the day, there's not much that can be done.

Meanwhile, it's worth noting that some students excelled at remote schooling. But most are reading at a level 3 grades behind.

tempest_ a day ago | parent [-]

The metaphor breaks down a bit when you consider that teachers don't generally get to pick their students while organizations get to choose their employees. Failing to choose the right employees is a failure of management.

foobiekr a day ago | parent [-]

Unfortunately many of the employees _most interested_ in remote work are such because they want to do things other than work.

Not all. I work with some remotes who are awesome. But the 24 year olds who want to work remotely from Thailand aren't getting their shit done.

nunez a day ago | parent | prev [-]

Seeing posts on here and Blind advocating for interviews to go back on-site due to cheating next to "RTO bad" posts is wild af.

It's wilder still that the handful of times I've dealt with this have all been before RTO!

martinald a day ago | parent [-]

I don't mean completely in person, but I do expect a lot of companies will want to meet the person in real life at least once. Which adds huge logistics problems.

Btw I'm not saying 'cheating', that's one thing. I am meaning industrial scale fraud with remote candidates. Eg having one person interview then another (much worse) person gets the job. There are gangs that are going to almost unbelievable lengths to do this.

alabastervlog a day ago | parent | prev | next [-]

About a year ago I moved to a new, largish company and, for the first time in my career, got to see how a company can be bad at remote work.

It's by being bad at work, period, but in ways that can be partially mitigated by being in-person. Poor documentation of processes, lots of know-the-right-person involved in getting anything done or figured out, using Teams (its design is remarkably awful for organizing and communicating within and among... teams) rather than literally any other notable chat system, et c.

This stuff is also making in-person work less efficient but it's easier to work around the problems when in-person.

Better than resisting remote work, would be for them to suck less at managing a business. Even if they continued resisting remote work, they should do that!

BeetleB a day ago | parent | next [-]

> rather than literally any other notable chat system, et c.

What is better? I hate Teams, but Slack really wasn't much better.

alabastervlog a day ago | parent [-]

Teams' core problem is that the actual Teams-section is more like a bulletin board than a chat system, almost like it was targeting that weird impulse companies had for a few years to build "company facebooks" or whatever.

The real chat part is cordoned off in ad-hoc channels that individual users can sticky, but that aren't "structural" and can't really have order imposed on them, if that makes sense.

It's like if Slack only had the DM and group-message feature, and no channels.

BeetleB a day ago | parent | next [-]

No arguments about the crappiness of Teams.

My thing is that while better IM systems exist, none is what I would call "Good" or even "Acceptable". Being better than Teams is not really saying much :-)

I haven't used Slack in years, so I can't speak to it, but it sucked when I used it. Back when our team was all colocated in one building, I intentionally had my IM app turned off and disconnected. Interruptions in person suck, but with Slack et al interruptions were multiplied significantly. Kind of: "If you can't be bothered to get up and walk to my cube, it probably wasn't that important."

What I want from Teams and similar SW:

A way to, with a keystroke, mark all messages as "Read" (even when focus is not on the window).

A way to, with a keystroke, print out all unread messages on my console (or in a popup window, or whatever).

In other words, just give me a damn API I can program these things with. Teams' API lets me get messages, but will not let me see if a message is read or unread.

Any app that forces me to open up the window, click on a dozen channels to read all the latest messages, sucks. Period. I should be able to read it all with one click/keystroke, and have them marked as "Read" when I do it.

Izkata a day ago | parent | prev [-]

Wait, what? We're moving to Teams soon...

This looks like channels do exist, is it new (there's no date on the page) or do they not work as you'd expect? https://support.microsoft.com/en-us/office/the-new-chat-and-...

scarface_74 a day ago | parent | prev [-]

And being in an office doesn’t help if no one on your team is in the same office. If you work in a large company that has multiple offices, you are still going to have the sane problem because eventually the person you need is not going to be in your office.

Even the small companies I’ve worked at (100-700 people) had multiple offices where you had to coordinate time to meet with the people you needed.

I’ve also worked remotely for the second largest employer in the US. Amazon has internal “interest” channels for each service team (the team responsible for an AWS service). Anyone could ask a question and usually one of the developers of the service would help.

nosefrog a day ago | parent | prev | next [-]

At Google, they found that engineers L5 and above got more work done with RTO, and engineers at L4 and below got significantly less work done. WFH is great but it doesn't work for fresh engineers (who are often the most gung-ho about it as well).

dastbe a day ago | parent [-]

Did you mean L5 and above got more work done with WFH? Since the next sentence implies that it was the fresh engineers who were most impacted by WFH.

nunez a day ago | parent | prev [-]

I think it goes beyond bad management.

These are my disadvantages of working remotely. I say all of these things as an advocate for hybrid work arrangements and co-working spaces/satellite offices:

1) Some people work better in an office. Offices are literally designed for working anyhow.

2) Some people didn't, and/or still don't, have optimal conditions in their house to work remotely.

I've seen tons of people on camera (another thing some management likes to "encourage" by mandate) who are working out of bedrooms, closets, or other makeshift rooms in their house. This is just _asking_ for a constant barrage of distractions.

3) Some jobs aren't compatible with remote work. Examples:

- Tech sales (moreso for complex sales and expansions than new sales)

- Many people who work in the public sector (even before this administration's aggressive RTO campaign)

- Most folks doing hardware or embedded work

- Pretty much everyone that we interact with outside of our home on a daily basis, like front desk personnel, doctors, mechanics, retail and restaurant staff, etc.

This creates an unfair imbalance of "haves" and "have nots". It is also very easy for the "have nots" to typecast those who WFH as lazy, especially given some of the memes of people doing all sorts of other things during core hours.

4) Some people don't naturally communicate what they're doing over Slack. This is the one thing I'll blame on management is communication.

Weekly "15-minute" hour long standups and check-in meetings covered for people like this back when we worked in offices, but it can be easy for these checkpoints to slip in when everyone's remote.

Now, these meetings existing are, in and of themselves, signs that management can be improved. Between Slack/Teams/whatever, bug trackers, Git commit histories, Office 365/Google Workspace APIs and all of the other signs of life of people doing things, there are ways for the PHBs to check that people are doing things so that they can report the things being done to their PHBs so they can report to their PHBs all the way up to the board and investors.

It would be great if more companies invested more in their processes to make it possible to assess productivity without needing inefficient meetings. This would make it possible to be a high-performing company regardless of location.

But change is hard, and it's easier for senior leaders/execs to throw their hands up and say "this isn't working; back to the office, now", especially when those leaders are already traveling all of the time as it is.

(I know that the trope of CxOs who golf/eat steak dinners all of the time is common; my experience working with people at these levels does not completely reflect that.)

5) Work-life balance is so much easier to immolate when working remotely.

When your home is your office and your work apps are on your personal phone, it takes the mental fortitude of a thousand monks to not be "terminally online" at work.

"I'll just hop back on after I'm done with the kids/dinner/etc." is the new normal. It existed before WFH, but it feels so much worse now, as the technology needed to set this up is so much more pervasive (mostly MDM being mature for Apple devices and Android becoming much more secure at the cost of everything that made Android fun for us hackers).

This has the fun side-effect of making people who try very hard to keep work and life as separate as possible look like slackers even when they're not.

6) Establishing rapport and camaraderie is much harder to do remotely. This "just happens" when you're working next to the same people every day for months/years at a time.

This was most evident when I joined a new company after COVID to avoid an acquisition. Almost everyone was super tight with each other because they hung out all of the time. There were so many inside jokes/conversations/memories that I was basically left out of, and because traveling was impossible then, forming new ones didn't really happen.

I get that many on this board view this as a feature, not a bug, but friends at work is important to some (most?) people. It's the one thing I miss from the before times more than anything else. Well, that and traveling all of the time!

7) Last thing I'll say on this: onboarding, in my opinion, is much worse when done remotely.

I've switched companies four times since COVID. ALL of these onboarding experiences have had some combination of:

- Loads of training materials, like labs and new hire sessions, that are dry as toast over Zoom but can be extremely engaging in-person,

- Some kind of buddy system that falls apart because everyone is drowning in a sea of Zoom meetings and the last thing people want to do is have ANOTHER zoom meeting explaining things about your new job that are kind-of difficult to explain without shadowing, and

- An assumption that you are a self-starter who will learn how to do your job by self-organizing meetings with people and scouring whatever documentation/knowledge/recordings/etc you can find.

This might just be a 'me' thing, but I've found remote onboarding to be a poor substitute for onboarding at an office somewhere.

scarface_74 a day ago | parent [-]

> I've seen tons of people on camera (another thing some management likes to "encourage" by mandate) who are working out of bedrooms, closets, or other makeshift rooms in their house. This is just _asking_ for a constant barrage of distractions.

At home, there have never been more than three other people in my house, when I’m “at work” with my door closed, they knew not to bother me. At work in an office there are constant distractions.

As far as “tech sales”. I’ve lead my share of complex cloud tech projects from discovery, customer acceptance to leading the delivery - all remotely. Yes sometimes I had to travel to the client’s site. But I haven’t needed to be in the office with the people on my team (who were sometimes in another country).

My coworkers are just that my coworkers. At work, “I’m taking a step back to look at things from the thousand foot few”, “taking things to the parking lot”, and “adding on to what Becky said”. I’m a completely different person at home. At the end of the day, my “friends” at work are not interested in keeping their jobs. I go to work to make money - not friends.

I’ve worked for two companies remotely since 2020 - Amazon and now a much smaller company. They both had excellent onboarding procedures. While AWS wasn’t “remote first”, my department (Professional Services) was as is my current company. Both had “onboarding buddies” and Amazon had a list of people you should set up 1x1’s with an instructions for the relevant internal systems you should use.