I'm not sure when you worked remotely but I can tell you remote work in 2014 is much much different. First off, using email internally for communication makes no sense. If you're a truly distributed team[1] you use teamspeak, or hangouts, or slack, or IRC, or anything other than email.
Second there are no radically different timezones within the US. If you're on the east coast you work most days from 10 - 6, if you're on the west coast you work most days from 7 - 3.
Third if you're working on something pressing with your distributed team you schedule some time together to work later. If you're on the east coast you may have some nights during a sprint where you're wrapping up at 9pm or 10pm.
Fourth no matter where your team is located if you have members in different US (or even international) timezones you want at least 4 hours during the day spent together (employees are really only performing at the top of their game for a fraction of the day anyway [2]).
[1] A truly distributed team is one that supports remote workers via communication and culture as much as they do their local employees.
Second there are no radically different timezones within the US. If you're on the east coast you work most days from 10 - 6, if you're on the west coast you work most days from 7 - 3.
Third if you're working on something pressing with your distributed team you schedule some time together to work later. If you're on the east coast you may have some nights during a sprint where you're wrapping up at 9pm or 10pm.
Fourth no matter where your team is located if you have members in different US (or even international) timezones you want at least 4 hours during the day spent together (employees are really only performing at the top of their game for a fraction of the day anyway [2]).
[1] A truly distributed team is one that supports remote workers via communication and culture as much as they do their local employees.
[2] http://cs.stanford.edu/people/eroberts/cs201/projects/crunch...