3 ms·
One really annoying factor about collaboration across timezones is trying to get schedules to sync up. Especially if there is an 8+ hour difference. Back and fo
by sxp 14y ago
One really annoying factor about collaboration across timezones is trying to get schedules to sync up. Especially if there is an 8+ hour difference. Back and forth communication ends up taking much longer and can significantly slow down the project. One interesting solution was examined in Cory Doctorow's Eastern Standard Tribe [1] where online communities form based on the sleep cycles of people rather than their location.
It would be possible for remote workers to use melatonin supplements and light therapy to intentionally manipulate their sleep schedules to sync up with their HQ if they are willing to tolerate the offset from the local schedule. Even more interesting would be if everyone switches to something like Uberman [2] so that working at various timezones becomes feasible.
[1] http://en.wikipedia.org/wiki/Eastern_Standard_Tribe http://en.wikipedia.org/wiki/Eastern_Standard_Tribe
[2] http://en.wikipedia.org/wiki/Polyphasic_sleep http://en.wikipedia.org/wiki/Polyphasic_sleep
- pavel_lishin 14y agoAs I understand the various Uberman schedules, skipping a nap is a pretty serious issue - might be hard to schedule meetings that don't happen to cut into anyone's sleep schedule.
- CodeCube 14y agoYes, sometimes the timezone difference can be difficult if the two parties are not equally as empowered (or even as good). But I'll give you an example. A guy I was working with decided to transfer to my company's singapore office (12h difference). Working with him was awesome! I could be working on something all day, then write him an email on where things where at EOD, along with things I wanted him to take care of. When my morning rolled around again, everything was done, and I had an email from him sitting in my inbox of stuff I needed to look at. Our work was getting done literally 24 hours a day :P