As I have a list of cities for remote companies, I thought I'll look into time zones as well. I was able to fetch time zone details for each city from the Google Time Zone API. Then I counted different time zones for each remote company and put the number on their profile (under Fun Facts).
You'll find TOP 10 on the stats page:
I wonder how you handle communication in your team when your members are spread across tens of different time zones.
Any tips on how to manage remote team communication with so many different times on clocks?
Great question, Rauno! For us at Doist, this begins with written communication (in Twist) as the default means of communication, because what is written is known and remembered. This enables communication to be transparent so that anyone who wasn't online during a "live" conversation can still see the progression of the conversation that took place and contribute once they are back at work.
Sometimes this means that a task of decision gets delayed a little bit longer than it would be if we were working synchronously, but it's a small sacrifice to make to allow the team to find balance between deep work and collaboration/communication. Having certain norms like responding to threads within 24 hours when a response is needed also helps ensure that things keep moving within a reasonable time frame.
Written communication also has other benefits. For example, when I joined the team, I was able to go back and read old threads from months and years prior to when I started to learn about certain things that were discussed or attempted in the past. This is a level of insight that would be difficult to gain in a traditional company because many of these conversations would have occurred verbally or through less-accessible communication platforms.
Thanks for a thorough answer, Andrew! I really like this approach – written async communication in threads. As I understand, Twist (product by Doist that you use) is basically built around this logic so teams can organize their conversations into threads instead of chatting on a Slack channel.
This makes very much sense: conversations are grouped by a topic in a thread and you can always go back to read them (also new team members). You can never do that on a Slack channel.
Twist is already doing great I see (100k+ teams using it) and it will definitely keep growing!
We actually just published an article all about async communication yesterday that might be of interest to others who are curious about it :)
Thanks, great article! I see @RemoteMatt also found it:
I've now also posted it to the /stories page with my comment: