When working in a distributed environment or remote work environment, as is increasingly – and quite fortunately – becoming the default for knowledge workers, and the software industry in particular, chances are, rather sooner than later you’ll be collaborating across timezones.
I’m currently collaborating with people from EDT, GMT, CEST, MYT, JST, and AEST timezones, for instance.
Asynchronous communication is crucial in a remote work setting already when no time differences are involved. It becomes absolutely vital when people from different timezones depend on each other’s results since in that scenario you simply can’t expect everyone to be working – or awake, for that matter – at the same time.
Arc, who amongst other services, run Codementor (a service I’m using myself for providing software development mentoring sessions), have published a useful best practice guide on How to Work Across Time Zones as a Remote Team.
The guide emphasises the importance of asynchronous communication (i.e. proper documentation or pre-recorded videos, for examples) and provides quite a few tips as to how to actually implement asynchronous communication processes, as well as case studies from long-time remote work proponents like Zapier.