4 ms·
Being unreachable during core business hours is definitely a huge problem from the perspective of the non-remote employee (me) who's in the office for the typic
by CydeWeys 9y ago
Being unreachable during core business hours is definitely a huge problem from the perspective of the non-remote employee (me) who's in the office for the typical eight hours a day trying to get something done and being blocked by a coworker who's unreachable because they're remote. If you a remote worker, the onus is on you to never let the fact that you're not in the office become a burden on your coworkers. If you end up being harder to work with because you're less reachable then your coworkers will begin to resent you for it, and that doesn't lead down a good path.
If you're not online and available during the expected business hours for your position then you're not really doing 100% of your job, because you're not able to assist your team members as is expected of your role.
Note that this applies to members of standard software engineering teams, and not necessarily to contractual work that involves delivering products on certain timetables but not necessarily close collaboration with a team.
- sbov 9y agoLots of places offer flexible business hours, even for people coming in the office. Not everyone always takes lunch at the same time either. Even people in the office are not 100% available all the time. Your attitude towards remote workers seems unnecessarily hostile.
- CydeWeys 9y agoYou're misinterpreting my post. At my current job we are flexible -- people come in and leave at different times, eat lunch at different times, etc. I'm not expecting everyone to be at their desks from 10-6 all day every day. That's why I said "core business hours". There's a difference between someone who is unavailable because they're off eating lunch and someone who is incommunicado for many hours at a time and impedes progress. I've seen remote workers drastically slow down progress by simply being unavailable while all of the non-remote workers are present and blocked on them for something. In theory an onsite worker could do this too, but in practice they don't simply disappear for hours at a time at the office.
- sbov 9y agoOur team is usually fully remote. I've actually worked my full career in mostly remote positions (15 years now). I've very rarely experienced people randomly disappearing for hours at a time, and usually a simple text will clear things up. However, if you work in a flexible office and your team has core business hours, official or not, your manager should probably convey this. This just falls under "managing expectations", and is not necessarily a failure of the employee. Sometimes emergencies will necessitate missing even core business hours. This is more a matter of having more responsibilities (family, kids, etc) than being remote though. But if an employee has these sorts of responsibilities, I'm guessing they are more likely to take up remote work. There are positives and negatives to hiring remote workers, and I think there are several ways to compensate for the negatives. Obviously since I work remotely I think the positives outweigh those negatives. But I also think placing so much emphasis on one of the negatives, that I rarely experience in practice, is extremely narrow sighted. But maybe your remote workers are bad at working remotely, maybe your company is bad at managing remote workers, or maybe there's confounding variables like the one I mentioned above.
- CydeWeys 9y agoI think the answer is that the remote workers were just bad/slackers/not devoted to their jobs. As I said, they failed to move upwards in the company and some were even fired. This was not at a company that was a particularly good or high-paying place to work, mind you. Maybe you've been luckier in the caliber of people that you've worked with, but I contend that, in general, across the entire workforce, it's not rare to see people taking liberties with remote work.
- biztos 9y agoI'm a remote worker and I'm sure it's occasionally a pain that I'm at the gym, or sleeping, or otherwise not responding on Slack or whatever. However, like many remote workers I work in a distributed team across several time zones. So it's not just "he goes to the gym in the afternoon," it's more like one person leaves the office in one time zone in order to beat the traffic jams, while another person in another time zone has to pick his daughter up from school, another in a third time zone gets up really early but can't do night calls because of family life, and so on. Slightly wonky schedules actually give us more coverage in case of crises, and the only way we could ever line everybody up for the same work hours would be to fire half the team. We manage it all pretty well by scheduling our meetings in advance, not being afraid to pick up the phone, taking ownership of our work, and having senior people in different zones who can help fix urgent problems. (However I totally agree with the "need for trust" comment above. I worked locally before going remote in this job, and also in two of the three other remote jobs I had in the past.)
- CydeWeys 9y agoDistributed teams across multiple timezones is a bit of a different situation though; you're naturally going to be more asynchronous there, and the team structure will be different. All of my experience with remote coworkers has been on collocated teams with the occasional remote worker in the same timezone. I don't have any interest in being on a fully distributed team; I like being physically present with my coworkers and I tend to get depressed ("cabin fever") if I'm alone all day every day. I realize that that might work for others, but it doesn't work for me, so I'd never do it.
- disc_magnum 9y ago> I tend to get depressed ("cabin fever") if I'm alone all day every day I think we found your problem
- CydeWeys 9y agoHumans are social animals. It's not just "my" problem, it's "most people's" problem.
- dasmoth 9y agoThat's certainly a way of working, and if that's what you've agreed too then certainly you should be as available as possible. There are more asynchronous ways to do things, and not always restricted to contractor-style arrangements. Personally, I think it's unfortunate if the default way of working assumes such tight coupling: for me at least, it's inimical to achieving any kind of deep focus.