Elevate Spring Summit has been announced (Thu, Mar 11th)

🔥


Don't have an account? 

Scaling a remote team from 4 to 40

Salary / Work Conditions
Scaling Team
Handling Promotion
Personal growth
Remote
Delegate
Internal Communication
Reorganization
Cultural differences
Hiring
Fairness
Team processes

16 April, 2018

David inherited a remote team used to fighting fires for the CEO. He tells us how he stabilized, scaled, and gained the trust of this team from afar.

Problem

Several years ago, I joined an organization whose main engineering workforce was abroad. The team was used to a reactive approach, responding to fires and building rapidly using rough mock ups and product specs. As the company expanded, I needed to find a way to scale and grow this team while "keeping the ship afloat" and ensuring everyone remained happy and autonomous.

Actions taken

My main focus from the beginning was to listen and observe what was working and not working for the team, noting problem-by-problem what issues people had, including too much firefighting, feeling overwhelmed and demoralized, feeling the product constantly changing, and needing more thorough product specs. I had several "affinity diagram" brainstorm sessions to allow the team to express their concerns and frustrations anonymously as well as proposing solutions. My focus was not on judgment but on understanding, listening, and empathy. In addition, through observation and a deep-dive of the code, I identified issues the organization did not see, including a monolithic application structure that needed to be broken into microservices, adding support for modern scaling technologies (caching layers, Redis, ElasticSearch, etc.), and changing a significant number of "silent failures" in the codebase to "fail loudly" instead (which resulted in many email alerts that over the months declined as they got the attention they needed). To gain the trust of the group, I flew to visit them and spent time to get to know them outside of working, being vulnerable and sharing about my personal life in a way that caused them to open themselves and connect on a deeper level. By fostering this more personal connection and doing a lot of hard work myself diving into the codebase early on and helping where the team needed it, I proved that I'm both human like them and a hard worker like them. As a result, they began to reveal concerns about other team members that they used to hide, and over time as we got closer, the team grew happier and more comfortable. After identifying and empowering the most talented among the group, I focused on mentoring those interested in management to hire and grow their own groups, focusing on autonomy of their team members (as this is one of the key indicators of employee happiness). We do daily standups as a "leads & managers" team and we regularly post-mortem issues both small and large to ensure we learn from our mistakes in a non-judgmental way. Not only did I have to gain the trust of this group, but in observing their day-to-day, there was a great deal of structure that needed to be added to streamline and de-stress the organization.

Lessons learned

Business is business, but it's between people, not robots. If you are unable to be physically located with a team that you're growing, you have to occasionally visit them and find ways to connect with them on a more personal level. In addition, by sharing vulnerably, as research shows, you generate oxytocin in the person you're communicating with and significant increase the likelihood that they will share and be vulnerable as well. This will enable you to gain trust and, hopefully, influence of the team. Also, you have to work as hard as they do, or they will never respect you.


Related stories

Learn or Die!
12 January

Marian Kamenistak, VP of Engineering at Mews, outlines key recommendations and resources to make learning an integral part of the engineering role and knowledge sharing across the company a steady practice.

Personal growth
Coaching / Training / Mentorship
Marian Kamenistak

Marian Kamenistak

VP of Engineering at Mews

Horizontally Scaling the Engineering Organization
11 January

Ken Pickering, VP of Engineering at Starburst Data, explains how to structure a product engineering organization to maximize results and address inefficiencies through horizontal scaling.

Scaling Team
Team processes
Ken Pickering

Ken Pickering

VP, Engineering at Starburst Data

Hiring for a Director of Engineering
11 January

Ken Pickering, VP of Engineering at Starburst Data, outlines what skills and qualities he looks for in a candidate applying for a Director of Engineering role.

Leadership
Hiring
Ken Pickering

Ken Pickering

VP, Engineering at Starburst Data

Cultivating the Company Culture in a Hyper-Growth Startup
11 January

Ken Pickering, VP of Engineering at Starburst Data, emphasizes the importance of cultivating the company culture -- particularly its most important aspects -- during a hyper-growth phase.

Company Culture
Hiring
Ken Pickering

Ken Pickering

VP, Engineering at Starburst Data

Creating an Evolving Process to Address Customer Issues
11 January

Sabeen Syed, Senior Engineering Manager at HashiCorp, explains how she initiated a process to address customer issues by creating a community engineer role that further evolved over time.

Users Feedback
Team processes
Sabeen Syed

Sabeen Syed

Senior Engineering Manager at HashiCorp

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.