2 ms·
I think the problem with those companies is that they used to think they "NEEDED" the people on site, so they never bothered to setup a culture of written and a
by vladvasiliu 7y ago
I think the problem with those companies is that they used to think they "NEEDED" the people on site, so they never bothered to setup a culture of written and asynchronous communication. So when the current crisis pushed them to WFH they were completely unprepared for it. Of course when this will be over they'll want people back on site: "See how terrible WFH was? We need to have people on-site working face to face"
- eequah9L 7y agoCuriously this "must be on site" mentality seems to be ripe even in some companies that have many offices, and people are de facto remote relative to each other anyway. Getting a "you know, I'm not sure this remote thing can work" from an architect that spends about half of his time on the phone just makes you go "what?" Dude's so busy calling everywhere that he's difficult to get hold of, but "remote can't work"? My experience has been that few people drive to the other side of the campus for a run of the mill chat or some random presentation. Unless it's in the same building, and unless it's something important, you just call, mail, chat, send office365 links, do skype presentations... you know, the remote stuff. So above a certain size, it's in the company's best interest to embrace remoteness anyway.