Remote software developers
I recently found myself wondering about what would be the reasons why most IT companies don’t like the idea of having its employees working remotely.
From the top of my head, and playing a devil’s advocate role, I can come up with:
- Working remotely gives you an excuse not to work;
- You are more easily distracted;
- I cannot just go to your desk and discuss something with you;
- I cannot control what you do.
I’m probably missing some, so feel free to comment on that and I will add them.
Let’s try to dissect all of those, one by one:
- Working remotely gives you an excuse not to work. Fair enough. You are not present and – as such – can do whatever the hell you want. But you cannot not work. At least if you want to keep your job, that is. The main problem here – I believe – is just a matter of perception. You can keep track of someone’s work just as easily remotely or on the same building. IT people have it especially easy, since their deliverables are typically in the form of source code (it’s pretty easy to track changes).
- You are more easily distracted. A fairly good point. I’m not going to say it’s not true, especially if you work at home. Your daily life can easily get in the way and it will take an extra amount of effort to keep them separated. But that is not to say that it cannot be done. Moreover, you will eventually find that the person will feel more motivated, even enough to put in more time and/or work outside work hours.
- I can’t just go to your desk and discuss something with you. This is a no brainer. Ever heard of Skype? MSN? Google Talk? Email? What about Google Wave? Need I say more?
- I cannot control what you do. Again, see point number 1. In software development you can. It’s pretty easy to keep track of what people are doing, especially if you use agile methodologies (like Scrum) in your daily activities. Get people to meet everyday in a room with Skype and do rounds talking about what was done the day before and what the plan for the day is. It does not get any easier than that, keeping track of people’s work.
So my question is: How come more IT companies are not doing this? It reduces their electricity bills, their water bills, the amount of money spent on office supplies, etc. I could go on, but you get my point.
Related:
- Software does not evolve; software degenerates Today at lunch i felt taken by this concept once...
- VLC for OSX developers needed According to a post on their forums, there are currently...
Categorised as: complaints, exploration, observations, technology
[...] This post was mentioned on Twitter by Pedro Assuncão, martimramos. martimramos said: RT @nocivus: New blog post: Remote software developers http://diffract.me/2010/01/remote-software-developers/ [...]
Pedro,
I’m guessing you are talking about Portuguese IT companies, right?
And if that is the case, the answer is simple: it’s very difficult for Portuguese managers to coop with it because they immediately associate working from home with working from a beach in the Caribbeans or something similar and it is very difficult for them to grasp why are YOU on a beach while they’re stuck at the office…
Borderline: they’re idiots…and have THE Portuguese gene
)…
Best,
Luis
Actually no, it also happens here in the Netherlands. But you did bring up an interesting point. Maybe it comes down to jealousy, who knows?
Yeah, that’s probably it ;o)
You did bring up interesting (and very logical) arguments…i also do not understand why we do not see more companies relaying on “telework” as it clearly has advantages for a great deal of professions.
And, just like you mentioned, if you do not work IT will (or should) be noticed!
So i really think it IS a jealousy issue (and the fact that upper management thinks they will get more work done if they can keep an eye on you)!
I actually saw a documentary about a company who restructured and allowed all the employees to work under a flexible schedule (part time remote, part time local) and productivity went through the roof!
The employees said they felt a lot more relaxed because they didn’t have to get up as early in the morning, had time to go jogging and didn’t have to get stuck on traffic which made them A LOT more productive! ;o)
Hugs,
Luis
By the way, off topic but…i really like your blog!
The design is really cool and very well structured!
Thanks, I actually took a great deal of inspiration from the blog of Tim Ferriss. Don’t know if you know about him, but he wrote an awesome book about subjects such as this one.
http://www.fourhourworkweek.com/blog/
I’m a remote software developer, so I’ll chime in on these.
1. Working remotely gives you an excuse not to work. I’m paid hourly, so if I don’t produce enough for the amount of time I bill, I get the axe. But, really, no one needs an excuse not to work. It’s just as easy to argue that having co-workers to talk during the day is an excuse not to work. After all, if we’re caught, we can always say we were talking about work.
2. You are more easily distracted. I’ll concede this one because it’s something I have to work hard with. Some days I can block everything else out and be completely productive. Other days, I’m constantly distracted. However, this isn’t actually much different from the cycles of focus and distraction one has in an office environment. The biggest difference is that the threshold for being distracted may be lower when working at home.
3. I can’t just go to your desk and discuss something with you. You missed the underlying issue on this one. The bulk of our communication with other human beings is encoded in body language, inflection, tempo, and other meta aspects that don’t translate into text-based communication. It’s hard to communicate with somebody you know only through text, but text communication is easier if you know them already. Some companies mitigate this by requiring remote employees to first work on site for a while before being remote. I’ve seen this issue bite teams enough times to know that it’s a real concern.
4. I cannot control what you do. That’s something a micro-manager might say. Good managers know that they don’t control, they enable and motivate. And generally, it’s good to avoid hiring the people that need to be micro-managed as they will lower the group’s productivity.
You have a point on the body language issue. Hiring someone immediately to allow remote work might be a mistake more times than it’s not, granted.
As for micro-managers … let’s say I’ve seen my share
Thanks for the input