Elevate Winter Summit has been announced (Fri, Dec 11th).

🔥


Don't have an account? 

How To Work Effectively with Distributed Teams

Remote
Health / Stress / Burn-Out

30 May, 2019

Ardy Dedase demonstrates the difficulties of working across timezones while also remedying the situation through company-wide implemented guidelines.

Problem

The concept of distributed teams is prevalent nowadays in high-growth tech companies. It's inevitable that in the span of your tech career you'll have the opportunity to work with or lead multiple teams across multiple time zones. There was a point in my career where I needed to work closely with people and teams from across different office locations: Edinburgh, London, San Francisco, Shenzhen, and Singapore. This situation led to me being spread thin across my responsibilities as an engineering lead and manager. It also caused some of our teams to stay late at the office, delayed deliverables, miscommunication across teams, and misalignment in our collective goals which caused further delays.

Actions taken

We came up with the following guidelines and shared them across our organization.

  • Separate work streams for different locations. Collocated teams can have similar work streams whilst minimising dependencies of these work streams between different locations. We are all for collaboration, but for distributed teams we'd like to have as much autonomy as possible for each collocated team or group of teams and reduce dependencies between locations.
  • Get to know your remote colleagues and build personal relationships. Spending time in person is not always possible but it's the best way to build rapport. At least make an effort to spend one to one conference calls with your remote colleague especially if you'll be working closely together. Start by having an introduction conference call to break the ice and kickstart the relationship-building.
  • Negotiation and compromise should come from all teams regardless of location or office size. Different sides of the world will need to give while others will need to take. For example, there are times when our U.K. based teams will need to wake up early while our APAC based teams will need to stay late at the office.
  • No last minute changes or requests. People have adjusted their schedule either to wake up very early to jump in the call or to skip their dinner appointment so they can join the synced-up conference call. If you really need to change or cancel the meeting give at least 24 hours notice. Your colleagues will thank you for giving them their time back.
  • Treat your documentation as part of your product. When your team in Singapore is sleeping, the source of truth of how your products or how to use your API will be its documentation.

Lessons learned

  • There will be cases where it will be impossible to compromise without taking a toll on people's personal lives. One example is the dynamics between teams that are in timezones without reasonable time overlaps like San Francisco and Singapore. For such cases it's best to structure your teams and meetings in such a way that there is no need for overlap between locations that are in the opposite sides of the globe. For example, schedule meetings and set work streams that are meant to optimise between Singapore and London, then London and San Francisco.
  • Default to asynchronous communication through usage of tools like Slack and Confluence. Reserve only necessary occasions to jump in a conference call for a meeting. Examples:
  • Leave your questions in your Slack channel before you go home. Then, best case is you'll have an answer the next morning when you come back. Not so good case is someone saw your question but didn't know the answer and will hopefully tag someone else who can help.
  • Write a Confluence document of your plans with a breakdown of tasks. Share that to your remote colleagues before you go home and ask them to leave their comments on the document.
  • Revisit and revise your working guidelines regularly. What worked yesterday might not work today.

Related stories

A Company Merger: Two Locations and Multiple Challenges
26 November

Matt Pillar, VP of Engineering at OneSignal, recalls how he helped merge two engineering teams at two different locations and how legal and cultural context made all the difference.

Company Culture
Cultural differences
Team processes
Team reaction
Remote
Matt Pillar

Matt Pillar

VP Engineering at OneSignal

How to Be a Great Leader in Times of Crises
30 October

Paulo Moncores, Senior Engineering Manager at Shopify, reflects on the crises unleashed by the outbreak of Covid-19 and offers his take on what a great leader should do in times like these.

Remote
Leadership
Internal Communication
Paulo Moncores

Paulo Moncores

Senior Engineering Manager at Shopify

Hiring 100 Percent Online With a 100 Percent Success Rate
30 October

Alvaro Moya, VP of Engineering at Wefox, underlines the importance of giving/receiving feedback during the hiring process and how it helps hiring the right fit.

Hiring
Feedback
Remote
Alvaro Moya

Alvaro Moya

VP of Engineering at Wefox

Creating a Healthy Remote Environment
30 October

Alvaro Moya, VP of Engineering at Wefox, shares how the Covid-19 pandemics gave rise to an opportunity to create a healthy remote working environment that will outlive the current grim moment.

Remote
Alvaro Moya

Alvaro Moya

VP of Engineering at Wefox

Remote Onboarding: A New Reality?
12 October

rabha Matta, Senior Product Manager at SquareTrade, recalls her recent remote onboarding and compares it to her past in-person onboarding experiences.

Onboarding
Remote
Prabha Matta

Prabha Matta

Senior Product Manager at Square Trade

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.