When More Engineers Means Decreased Productivity
7 June, 2018
When we first started Chartboost, before we raised money, the whole company consisted of just me and another engineer. We were knee-deep in coding and building things and were incredibly busy. Once we raised money, we were able to hire engineers, so we went from a team of two people to a team of six. It was much more challenging to have a team of six people be as productive as a team of two.
It took about six months to get to a point where our team of six people was as productive as we had previously been. This seems really counter-intuitive. Surely, adding more smart, talented people to the team would increase productivity. However, the process of running a team of six is so different from having just one other person working beside you.
When you are only working with one other person, you tend to already be aligned, just by the nature of your dynamic. With six people, it's more difficult to ensure that everyone in the team has a full picture of what is going on. It's important to add more structure when this happens and to ensure that people own tasks and projects. By the time we had grown to a six-person team, we had built quite a few things. Not everyone on the team could be a pro at every single thing we had built, so we had to spend time working out who was good at what, and who was okay at what (but could act as a backup).
Adding more people to your team doesn't always translate to increased efficiency. There will always be growth milestones that completely change the way you have to work. When going from six to 15 people, we faced a new set of challenges, and the same happened when going from 15 to 40 people. As you grow, how you structure your team has to be constantly adjusted and reenvisioned.
Michael Mac-Vicar, CTO at Wildlife Studios, dissects how to set guardrails that would contain the exponential increase in cloud costs.
CTO at Wildlife Studios
Michael Mac-Vicar, CTO at Wildlife Studios, explains how the tension between Technology and a business unit creates an equilibrium of competence that helps solve the problems most efficiently.
CTO at Wildlife Studios
Shikhar Bajaj, Senior Product Manager at VMware, discusses how he developed a product mentality in his engineering-centric organization by introducing a formal stage-gate process that included the business review.
Sr. Product Manager at VMware
Mason Mclead, CTO at Software.com, delves into how to take care of tech debt while pushing out new features and products.
CTO at Software.com
Marian Kamenistak, VP of Engineering at Mews, explains why EMs shouldn’t be measuring the output of a team or individual engineers, but the outcome of the whole team.
VP of Engineering at Mews
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.