3 ms·
I've worked remotely off and on for the last 10 years. I'd say at least half the time I have been out of the office. I have managed remote teams in Mexico, Ukra
by jconley 14y ago
I've worked remotely off and on for the last 10 years. I'd say at least half the time I have been out of the office. I have managed remote teams in Mexico, Ukraine, India, Arizona, Switzerland and even randomly dispersed developers/artists all over the world. Remote teams can work very well.
What doesn't work very well is having a few remote people and a large mass of people in an office all working together on the same project. There is significant high bandwidth communication that happens when people are together physically. This leaves remote workers out to pasture. Things get missed. Tension builds.
The same effect occurs when you have multiple offices working on the same projects. I've been in the middle of this first hand as well. You can quickly end up with teams doing a lot of internal communication without talking to the teams in other offices. Rivalries will build. It will probably become an "Us vs Them" situation as animosity over small things snowballs.
This can be combated largely by explicit written communication. Use chat rooms. Use good issue tracking. Use internal social networking.
- billpaetzke 14y agoI'm not following. What is the good use case for remote working? The remote workers need to be on an isolated project?
- jconley 14y agoIf the project requires a team it works best when the whole team is remote and/or extremely conscious of using written communication. That is, if you want the remote person to feel like they are a part of the team. If you have outsource contractors it doesn't really matter. You just tell them what to do in meticulous detail anyway. But, if you want a contributing team member that buys into the company, make sure they are included in all communication. The easiest way for this to happen naturally is if everyone is remote.