It is often perceived that the challenges in building a distributed team lie in communication over distance, however with todays incredible technology and tools the problem we have experienced is really one of communication across timezones.
At Sqwiggle we are currently spread across 2 countries and 4 timezones – it is this, rather than distance, that creates problems like confusion over meetings, not enough crossover time for discussions, odd working hours and more. I’ve become more and more concious of these things and tried to keep tab of the little things we do to reduce friction:
Keep communications in one timezone
In emails and spoken conversations try and pick one timezone and stick to it in all of your communications. This small hack makes a huge difference in stopping confusion, and you’ll always know which timezone you arranged your meeting in. Of course which timezone you pick is upto you, it could be where you are based, where most of your clients are or where your company is, just be consistent.
Use a shared calendar
A shared calendar such as Google Calendar provides a whole bunch of benefits, for a start each participant sees the event in their own timezone and in relation to their own day – a huge confusion buster. A shared calendar also has the advantage of increasing transparency within your team, you never know who might have input on a meeting or event that you wouldn’t expect.
Don’t spread your team too thin
When we began advertising our open positions we received a lot of applications from all over the world thanks to our “you must remote work” policy! This was great but we soon realised that at the size and stage of the company we would have to filter out some candidates purely based on location. This allowed us to reduce our timezone-spread and maximise time when the whole team is online.
Split your day in two
Right now we are beginning to deal with the maker / manager transition at Sqwiggle. In my experience so far, being based in Europe with over half our team in the US affords a distinctive split in the day where the morning is quiet and great for focus on coding tasks whilst the afternoon becomes planning, discussion and other non-maker duties.
Something’s gotta give
Even being very concious of these factors I’ve found that when working closely with a geographically diverse team the best thing you can do is increase the amount of crossover that you have for syncronous communication. This generally means one or both parties shifting working hours to accommodate more time spent working together. Sqwiggle has proven very useful in this respect and I often stay logged in until late into the evening, making me available for anyone on the team to ask quick questions that come up during their daytime.
Do you have any tips for working more effectively between timezones? Let me know in the comments, I’d love to give them a try