|
|
|
|
|
by humbleferret
794 days ago
|
|
I've seen two primary strategies for handling cross-time zone communication in teams: Synchronous: A single time zone is designated, and all team members adapt accordingly. Although, this can be a pain for people far away. Asynchronous: Flexible “overlap” periods are defined where everyone must be online. In practice, though, remote teams I've worked in just seem to understand and accept that:
A) You don't need a 'call', 'quick chat' or 'meeting' over video or voice most of the time
B) If you are in a remote team, there is shared acceptance that there will be A LOT of asynchronous communication and people will reply when they can or are available.
C) The situation changes the more time-zones you cover. Be flexible. Those with roles that are 'mission-critical' or 'perpetually online', are usually on call or have a phone that is always available. A handy resource for aligning schedules: https://www.timeanddate.com/worldclock/converter.html |
|