4 ms·
First of all, I'd like to applaud this initiative. I worked remotely for 4 years (just switched to a local startup) and it was great for work-life balance (amon
by yawz 10y ago
First of all, I'd like to applaud this initiative. I worked remotely for 4 years (just switched to a local startup) and it was great for work-life balance (among other things). I wholeheartedly wish that it would be very successful.
This may not be something new for you guys, as you've been running remote agile teams, but how are you planning to deal with time differences? Are you reserving the right to ask remote employees to start their day at a particular time? Are you going to take time zones into consideration when building your teams?
- bryanh 10y agoWe are already 100% remote and have been for the entire life of the company. Time differences haven't been a big issue - it can be tricky to get everyone on a call when they need to be - but usually a little flexibility by all parties go a long way. Also, you can arbitrage time differences to knock down annoyance from on-call rotations and the like. We ask employees to have their own "consistent" hours so that the rest of the team knows when they'll be available or not. We do consider time zones when hiring - for example, we might explicitly hire Asian/Pacific for support scheduling reasons.
- e40 10y agoAlso, you can arbitrage time differences to knock down annoyance from on-call rotations and the like. I have no idea what that means.
- detaro 10y agoIf you have people all over the world, nobody (or at least fewer people, depending on how the distribution works out) has to be on-call in the middle of the night, you can hand off close to the end of your normal working day.