5 ms·
It's very likely that if a company can't support remote work that they have other major structural problems. It's really not hard to have remote developers. Any
by malvosenior 7y ago
It's very likely that if a company can't support remote work that they have other major structural problems. It's really not hard to have remote developers. Any competent management structure should have no issue with it.
- ttoinou 7y agoYou need to switch all of your IT and meetings fully online. Doesn't sound easy if you didn't start from zero with that in mind
- ghaff 7y agoEh. Even if the company is a single office, I’m pretty sure people need to travel and need to be able to get online and have meetings when they’re not in the office.
- discordance 7y agoIt's not so trivial. If you have only one remote worker, you need to adjust the mindset of all their colleagues. A frequent example of this is having remote attendees in a voice/video meeting not being recognized, forgotten or just spoken over. Learning how to integrate remote employees and behaviors takes time to learn for any organization, even competent ones.
- malvosenior 7y agoI have to admit that I consider that a fairly trivial problem. I will say that the bar for quality has to be higher for fully remote employees. They must be somewhat self driven and mature enough to speak up and be heard when the time comes. Mediocre people can "hide in plain sight" when they're in the office every day. The lack of output or formal collaboration comes out more when they're remote and can't pretend to work/chat with colleagues all day long.
- ilaksh 7y agoI think that is a good point. For those reasons many have come to the conclusion that fully remote workforces using appropriate communication paradigms (usually written) are more feasible than partially remote.
- discordance 7y agoI work in a fully remote enabled team, and one thing we do to even the playing field is always join calls in separate rooms even if we're in the same building. Works well!