Plato

Login to Plato


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Don't have an account? 

When Words Bear More Weight

New Manager
Team processes
Collaboration
Internal Communication

27 February, 2021

Wissam Abirached, Senior Engineering Manager at GitHub, tells of his transition from an IC to a manager on the same team and how that impacted his participation in technical discussions.

Problem

When I was an engineer on the team I was able to participate in technical conversations and share my opinion like any other engineer on the team. However, as a manager, I no longer was able to provide my technical input or opinion because people on the team would take it as a directive as opposed to another, possibly divergent, opinion.
 

This is not what I wanted because we have smart engineers on the team who were more familiar with the technical architecture and day-to-day problems. Moreover, the longer I stayed on as a manager, the less I was involved in the code. They were more up-to-date than I was, and I wanted to empower them to be critical and don’t take my opinion as it was. At the same time, I had extensive experience being an engineer on the team and felt that my technical input would be beneficial. But people wouldn’t argue back or push on the manager’s opinion and were taking my arguments at face value.
 

Actions taken

What worked -- Be the one to speak last

I decided to be the last to speak in a meeting. I would sit back, take notes, and wait until everyone had given their opinion. If some of the engineers hadn’t shared their opinion, I would prompt them to see if they have anything to add. Only after everyone had shared their thoughts would I share mine too. All the opinions would then be laid out on the table. That allowed the team to hear different thoughts instead of having only me talking.
 

The privilege to be the last speaker enabled me to stir up the discussion. Sometimes I would have a certain opinion on things, but after hearing some other proposals, I would be persuaded that they were better than mine. I would make sure to emphasize that and how hearing all different opinions made me revise my own.
 

Sitting back and keeping quiet was not easy. I would listen to people share their thoughts and, on multiple occasions, would want to interrupt them and add my two cents, but I would remind myself to keep still.
 

What didn’t work -- Individual encouragement in one-on-ones

I tried to bring it up in one-on-ones and explain that taking my opinion for granted was not part of the culture I wanted to build on the team. I would explain how I wanted us to build a culture where we should share opinions, and they should feel free to push back on my or leadership’s proposals. I would acknowledge their expertise and their involvement in the code and encourage them to speak up.
 

While I am certain that this helped a bit, it never amounted to full acceptance. They would still wait for me to share my thoughts. I also tried to speak at the meetings by abstaining from speaking from a manager’s perspective. I would say, “I have some thoughts; it’s just an opinion and certainly not any final decision.” Prefacing my statement with an explanation simply didn’t work, and they did take it at face value.
 

Lessons learned

  • Leaders tend to take a lot of air in discussions or meetings. When they don’t listen, they unconsciously kill creativity, collaboration, and innovation, altogether. Your role as a leader is not to always come up with the best ideas but to provide more context and encourage collaboration. Because at the end of the day, the team is the one to build things, and you need to empower them to take part in those discussions. By sucking out air in the meetings, you do not allow your team to flourish, which will ultimately hurt the product.
  • Be aware of how much weight your words carry. Also, be mindful of how much time you are talking and how much time you are listening to others.

Discover Plato

Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader


Related stories

Four Common Challenges of a First-Time Manager
9 April

Leo Torres, Engineering Manager at Carta, outlines four common challenges he encountered as a first-time manager.

New Manager
Leo Torres

Leo Torres

Engineering Manager at Carta

Acting Quickly To Resolve an Incident
9 April

Leo Torres, Engineering Manager at Carta, speaks of his prompt response to a recent incident and how acting quickly allowed him to make a customer happy.

Leadership
Collaboration
Team processes
Leo Torres

Leo Torres

Engineering Manager at Carta

Cultural Meanders of Communication
9 April

Boris Ruiz, VP of Engineering at HealthCare.com, dissects four main challenges that made communication among his diverse teammates difficult.

Company Culture
Internal Communication
Cultural differences
Boris Ruiz

Boris Ruiz

VP of Engineering at HealthCare.com

Pausing for Innovation
31 March

Arjita Ghosh, Director of Engineering at Quizlet, shares how intentional pausing can instigate innovation and boost productivity.

Productivity
Team processes
Arjita Ghosh

Arjita Ghosh

Director of Engineering at Quizlet

Shipping Products Faster with Confidence
26 March

Ian Logan, VP of Engineering at Rose Rocket, explains why the speed of execution is critical for finding a product-market fit and highlights how to build confidence when shipping fast.

Dev Processes
Team processes
Ian Logan

Ian Logan

VP Engineering at Rose Rocket

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.