Skip to main content

Understanding "Emotional Intelligence" (or EQ) to Build Great Teams

Let me tell you… This has been my favourite subject of all! Not that I may want to do research in psychology but understanding people and how they behave so differently in different situations - just puts me in awe!

So… What is EQ?

A very nicely written post from psychcentral (Psych Central Link) aptly explains EQ as well as its 5 categories (or components), which are –
  1. Self-awareness
  2. Self-regulation
  3. Motivation
  4. Empathy
  5. Social Skills

With even more detail, positivepsychologyprogram (Positive Psychology Program Link) provides even more details with the 4 dimensions of EQ, which for ‘emotions’ are –

  1. Perceiving
  2. Using
  3. Understanding
  4. Managing

For further exploration on EQ, starting with Wikipedia (Wikipedia Link) is a great idea, since it also talks about the 3 models of Emotional Intelligence (or also referred to as EQ). The above 5 categories are coming from the “Mixed Model”.

I am quite influenced by the ‘Mixed Model’ than other models. It is much more comprehensive and connects with a 360-degree assessment. EQ is a great helper when doing appraisals for employees, but ONLY if it is done in the correct-way! Please await a separate write-up on this one.

For the 5 categories given above, a common and important trait of “awareness” runs across.

You shall find many trickles of this trait in the below paragraphs.

Why is EQ so important to build great teams?

In many articles online, I see one common conclusion – ‘EQ is more important than IQ’. In our daily work, when two or more people form a team, they need to work closely to resolve many issues, share knowledge to enrich and create a high-quality outcome. This cannot happen without an environment, that promotes –

  1. Respect for individual viewpoints and ideas
  2. Ease and openness of communication
  3. Freedom to individuals, and trust with responsibilities
  4. Ethical responsibility and actions
  5. Learning of new domains, processes and technology

Such an environment can be created, only with individuals who have the right ‘EQ’ (or attitude / mindset) for growth. A culture of positivity and growth is extremely important for individuals to give their best and remain motivated.

How can understanding ‘EQ’ help build great teams?

Many organizations look for leaders (and visionaries), who help create an organization culture, that promotes the kind of environment given above. Such leaders inspire and put the team ahead of them to achieve a common goal.

Some of the most important pointers to build great teams, that I have experienced are –
  1. Nurture leadership or hire leaders, who ‘walk-the-talk’ and understand their team based on their temperaments. Individuals come with a domination across the four personality types (Sanguine, Phlegmatic, Choleric and Melancholic). A mix of these provide clues of their dominating behavior. A matured leader understands this and behaves appropriately.
  2. Get individuals in a team (when hiring or moving), with a good variation in the number of years of experience. This helps the group do self-management (to resolve conflicts, build credibility, learn from others experience and get the right challenges forming inter-personal relationships).
  3. Provide strong support systems (processes and technology), that can strengthen the foundation of an enabling environment.
  4. Accept failures from individuals as a stepping-stone, for everybody to learn and move forward. Evaluate the ability for individuals to come-out and do better after failures. A smart use of failures to create organization-level best-practices indicates a culture of positivity and growth.
- Written by Anand Nanavati (SupraDigit Solutions)

Comments

Popular posts from this blog

The Top 4-Ways to Build the Right Test Strategy

A Test Strategy is created to guide all teams on steps to achieve software quality objectives. With software companies adopting agile practices in a big way, an effective Test Strategy becomes even more important with iterative / sprint-based application development. A test strategy being a live document, should ideally plan to integrate the business, development, testing, and management teams, define the quality objectives for the intended application and chart-out a path on how all the teams can help achieve these. The test owner and the team can build an effective test strategy with these 4 best-practices: A)   Focus on Prevention – Helps avoid major issues and rework on projects. ü Prioritize requirements and business rules. ü   Communicate changes in priorities immediately and effectively to important project stakeholders. ü Strictly review and implement common require

Reduce Your App Development Costs by More than 50% by "Simply Preventing Bugs"!

"Be a yardstick of quality. Some people aren’t used to an environment where excellence is expected.”— Steve Jobs Everybody loves to avoid a disaster, but there is a “proactive” effort to do activities that can prevent a disaster from happening. Most of the executives do not want to “get involved” in such “proactive” efforts, simply due to the love of fixing urgencies Or having a mindset that it’s not important.   I remember, when once I was working with the Quality Assurance team on a product. The development team simply refused to spend efforts on the most essential “unit testing” for their developed components! The intent was to release the software to the QA team as soon as possible and focus more on so-called “core development”. Over the years, looking at multitude of projects failing in-spite of highly experienced resources, reasonable time and the intent, I have uncovered that, prevention is the “Most Important” and “Ignored” part of software development. Why should we

What is Software Quality?

“Why do we never have the time to do it right the first time, but always have time to do it over and over after the first time?” – Anonymous  Quality is something that happens at every stage of Software Development! When I talk about Software Quality, almost everyone in the Information Technology world thinks about “Software Testing”. Unfortunately, this is a myopic view of Quality as a specific team effort and not as something, that should be embedded and part of the complete Software Development Life Cycle! Quality can be defined and need not be an “ambiguous term” for an organization. For any software, quality is more aptly seen from a view of what the customers considers as ‘Quality’. Although, this is not the only way to consider ‘Quality’. Quality must be seen from the viewpoint of ALL stakeholders involved with the product. Apart from this, ‘Quality’ should be considered as everybody’s res