Maintaining Productivity as a Quickly-Scaling Team
26 April, 2021
When first joining my current company, the start-up was very small — only five or six people. Now, we are a team of four hundred, an endeavor that took place over ten years. During this time, we have overcome many challenges in relation to scaling up so quickly. Even after dividing ourselves by platform, we found that the work called for more specialized teams, each devoted to a single feature.
As we introduced each new department, I would step in as a team-focused tech lead before moving on to build the next group. We now have a Division unit, a features-based unit, and platform-related teams that work to improve the health of the company overall, as well as to optimize developer productivity. All of these groups contain sub-units under their umbrellas.
During this time, one of my main challenges was maintaining the productivity of our developers and to continue to realize the goals of the company as the organization took on volume.
I led an effort called “Developer Experience”; this is the Division unit mentioned previously. It consists of two sub-teams: one handles performance, the health of the application as it exists for the user, and the other focuses on developer productivity specifically by developing reusable components. While developing each team’s strategy personally was a challenge that I enjoyed, being able to delegate in this way allowed me to manage many people at once.
After I had been with the the DevXP department for an entire year, we were introducing new features and tools constantly. Each new team had a dedicated EM, and each department now had its own engineering manager tasked with creating processes and best practices for the work of their teams specifically. I had never led such a huge organization before, but finally felt that I was able to match our pace of growth comfortably.
- You should never wait for somebody to teach you something or to show you the way. You need to research the challenge and to learn on your own. I learned to act and to avoid waiting. This gives life to all of my ideas.
- Do not shy away from any process that may solve the problem that you are facing, even if new and unfamiliar.
- Do not fear failure in your career. Every misstep teaches us something important. As long as we do not repeat our mistakes, there is no reason to avoid ambitions that scare us.
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Andrew Tsui, a Product Leader, works to build great teams that are independent, demonstrate mastery of their domain, and fully commit to their purpose.
Director of Product at Startup
Albert Lie, former Founding Engineer and Tech Lead at Xendit, shares his annual performance review process implementing principles from the Ikigai framework into regular check-ins.
Former Tech Lead at Xendit
Frédéric Duperier explains his process of pairing juniors and seniors to fill the knowledge gap and learn new techniques.
Founder at We Are One Sarl
Prasad Gupte, Director of Product at Babbel, shares his insights into the challenges behind successfully growing a team.
Director of Product at Babbel
Kirk Gray, VP of Engineering at McGraw-Hill, recalls his experiences performing major reorganizations of departments, including successful techniques to ensure a smooth transition.
VP Engineering at McGraw Hill
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.