Skip to main content

Ego in Your Decision Making

Oxford dictionary defines Ego as: “a person's sense of self-esteem or self-importance”. It says that it is “responsible for reality testing and a sense of personal identity.” For a lot of us techies those were really important functions that probably served us very well early in our career.  We had to be assertive, we had to choose a coding style guide, pick our frameworks and “be decisive”.  However when it comes to engineering management the same things that used to help might be turning into a liability.

When my job changed from writing code to creating an environment where the best code is written - it took me a while to understand how my ego was holding me back.  I kept applying the old tricks - defining the architecture, the final design and task priority.  What ended up happening is those things led me to turn off a lot of the best and brightest people on my early teams.

I remember the feelings of being aggravated when I had to go over an explain my decisions and get buy in from my team.  My ego was screaming “I am here because I know what to do, can’t these guys just trust me and move on already?”  The sense of control and righteousness eagerly served by my ego didn’t allow me to create space for other people to grow or willingly get on board.

At one point I had a great engineer on my team who was really innovative and my attitude ultimately led him to leave.  In a couple of weeks he wrote a new application that would probably take several people several months to get done.  The problem was that he chose a different framework than what we were already using.  I remember that I was actually upset because I thought about the pain of maintaining this application in case this engineer left.  No one else knew how to work with that technology and I knew that as a manager the responsibility of keeping it running was ultimately up to me. My sense of needing to be in control started pushing this guy away and he ended up leaving a few months after.

Cases like that taught me that I had to reframe my thinking.  Instead of being right technologically I had to start being of service to the folks who reported to me. I started evaluating myself on the basis of the team I create instead of the software I create.  A few times folks took wrong turns and got us in trouble, however when they did they also felt responsible to make it right.  Most of the time the environment retained super stars and they surprised me with their innovation.

Dale Carnegie wanted this inscribed on his tombstone: “Here lies a man who knew how to enlist in his service better men than himself.”  If you are starting in engineering management or feel like you hit a plateau - put a permanent sticky note with those words on your monitor.

If you liked this you might also like:
2 Way to Treat Your Software Engineers
Emotional Intelligence in Software Teams


References:
https://www.carnegiehall.org/BlogPost.aspx?id=4294980110 
https://www.entrepreneur.com/article/207642
Post a Comment

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …