Managing a team of engineers who are not technically aligned
6 December, 2017
When I started at Kabam as an engineering manager, I inherited a team which were not reliably shipping quality software. I collaborated with another engineering manager and his team to ship features for the same project. While the engineering manager and I fully believed in the benefits of test-driven development, my team was very reluctant about this approach. Because of these discrepancies, the development process was an operational nightmare.
We decided to pause product development and rebuild the application using Business Driven Development. We changed the technology stack from PHP to Ruby on Rails changed the process we used to release software. In a way, we imposed this decision on my team, which is not usually my preferred management style. The difficult part of this transition was getting my engineers to contribute in a constructive manner to this method, even though they didn't believe in it. We used a prototype, developed by one of the other manager's engineers, to prove to the rest of the team that it was more efficient to use the test-driven method. Making this significant change caused us to ship very few new features for 3 months, but allowed us to ship our software much more reliably and faster after change. We no longer had weekly releases rolled back frequently, but moved to a process of shipping when features were ready, often multiple times per week.
Working with people who are not aligned technically is very uncomfortable, and as a manager, you sometimes have to make hard decisions to make your project move forwards. Sometimes it is better to be criticized but to lead your team to success than to be loved but to lead your team nowhere. In these types of cases, I would suggest spending time with reluctant team members, to explain the reasons for your decisions as transparently as possible. If they are still not convinced, you should pay attention and try to prevent them from becoming a toxic influence on other team members.
Peter Berg, Founder and CTO at Forward, recounts how he introduced processes for continuous improvement and thus creating a more psychologically safe working environment.
Founder / CTO at Forward
Peter Berg, Founder and CTO at Forward, describes how he helped ramp up a slow-moving team by applying his simple, yet expert approach.
Founder / CTO at Forward
Caroline Parnell, previously managed product teams at O2 and Vodafone, shares some of the techniques she applied with her team to ensure diversity of thinking during product discovery workshops.
Most recently Head of New Product Innovation at Previously O2 and Vodafone
Justin Potts, VP of Engineering at MoneyLion, tackles the ever-intriguing problem of simplifying the architecture and thus reducing the overall complexity of the systems.
Head of Engineering at MoneyLion
Brian Guthrie, VP of Engineering at Meetup, recalls the difficulties he endured due to a lack of cross-departmental cooperation caused by different systemic incentives teams were given to.
VP of Engineering at Meetup
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.