▲ | bradleyjg 6 months ago | |||||||
I found being in the US east coast in teams spread across Europe and the US to have the advantage of being able to touch base with anyone fairly easily but the disadvantage of never getting that natural quiet period. I don’t see how us east cost <-> apac is really feasible on any kind of regular basis. | ||||||||
▲ | eitally 6 months ago | parent | next [-] | |||||||
It depends if you're a morning person or not. I used to manage teams in India & China from the east coast and it was usually a-ok having 2-3 hours of overlap each morning. It's FAR harder from the west coast and there's really no way around having evening (US) meetings since the alternative is asking the remote team to be in the office quite late. That said, this is also why many Asian teams get accustomed to working US hours -- essentially "2nd shift" -- to accommodate west coast overlap. | ||||||||
▲ | aragilar 6 months ago | parent | prev | next [-] | |||||||
I think daily/weekly you'd shift work hours (that what I do when I have a meeting like that). Global meetings are always a pain, though I'd say the worst meetings are when US-based folks plan a meeting based on their local timezone, as opposed to UTC, because it always ends up at 3am in Australia (so I bow out of those). | ||||||||
| ||||||||
▲ | ghaff 6 months ago | parent | prev | next [-] | |||||||
We had occasional interlock meetings, briefings, and webinars but it pretty much meant that from the east coast you were doing them at 10 or 11pm. I'm sure senior execs did more frequently. We didn't really have people on the west coast, especially latterly when I was there. Up to 5 or 6 hours is a reasonable range for routine interactions. | ||||||||
▲ | CoastalCoder 6 months ago | parent | prev [-] | |||||||
I did US East Coast / Shanghai for one project. We got really good at asynchronous messaging, and that went a long way. Still didn't fix the 1-workday latency for discussions, though. | ||||||||
|