Skip to main content

Emotional Intelligence in Software Teams

I generally get questions about API design, platform marketing and software management, but recently
I was asked something a bit different: “Which emotional intelligence traits do you value in your co-workers?” Good question!

In order to explain my perspective, I should first clarify the type of office environment I value. I work because I want to be in an exciting space; I want to be the best at what I'm doing, and run a team that’s committed to success. For these criteria to align, I need to work at a company that employs smart people with high intelligence quotients (IQs) in their respective areas of expertise.

However, even on software teams equipped with high IQs, having even one member with a low emotional intelligence quotient (EQ) can interfere with the entire team's ability to achieve project goals. Here are the top EQ traits I value on my teams:

1. Control your emotions. Nothing gets in the way of productivity more than someone “losing it” by getting overly caught up in their emotional reactions to a situation. If someone throws a chair across the office, the physical mess is a lot easier to clean up than the emotional one. What will frustrate me more than the act itself is if the entire company starts talking about it for a week, then my co-workers shift their focus off the projects that can further our shared goals.

2. Understand the perspectives of others. In sales, you need to empathize with your buyer if you want to turn them into a champion. In customer support, you need to understand that complaining customers are frustrated because they are experiencing difficulty using your product. In a meeting, you need to appreciate the variety of differing opinions and backgrounds of your colleagues in the room. Embracing these perspectives with openness and curiosity allows a team to collaborate creatively and uncover potential opportunities.

3. Be positive. Nothing was ever created by people who said "No" to work. "No" is a sure way to get nothing done. A “can-do” attitude enables people to explore and invent. It also comes in handy as a reminder to keep going when the going gets tough. Colleagues with this outlook exude positive energy that spreads to other team members and unites everyone around the excitement and attainability of the goal. This approach attracts positivity from others both within and outside of the company.

4. Share. Successful companies know how to share. Leaders who know how to “grow the pie” are the ones who attract and retain the best talent. Growing opportunity and sharing it is a way to build a bigger team with more talented people. A bigger team with more talent wins.

Screening for these EQ traits in an interview can be challenging, but it’s very much worth it! Surrounding yourself with people who have high EQs will make for a better journey and a better destination.

Post a Comment

Popular posts from this blog

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 …

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…