How to Coach People Into Leadership Roles
Tags: career, advice, leadership
Published: 2017-11-17 04:59:38

---
title: How to Coach People Into Leadership Roles
published: true
description: Every software engineering team requires doers and leaders. In my experience, for every five or six doers, you need a leader. It is essential for engineering managers to learn how to spot and coach people into leadership roles.
tags: career, advice, leadership
canonical_url: https://www.coderhood.com/how-to-coach-people-into-leadership-roles/
cover_image: https://thepracticaldev.s3.amazonaws.com/i/ioa3o4hiyw5e7vo0bc6w.jpg
---

This post was first published on [CoderHood](https://coderhood.com) as [How to Coach People Into Leadership Roles](https://www.coderhood.com/how-to-coach-people-into-leadership-roles/). CoderHood is a blog dedicated to the human dimension of software engineering.

[![](IMAGE-URL)](https://www.coderhood.com/how-to-coach-people-into-leadership-roles/)


You Need a Balance of Doers And Leaders
---------------------------------------

![](https://thepracticaldev.s3.amazonaws.com/i/pgdn7fku3acvkmsxl2dj.jpg)Every software engineering team requires doers and leaders. In my experience, for every five or six doers, you need a leader.

Engineering teams with too many leaders tend to fight about direction, vision, and control; as a result, they get very little done. The work environment is crippled by turf wars and constant attempts to reach consensus. Whatever they ship, ships late and looks and feels bland and designed by committee. Thankfully, having too many leaders is not a common situation.

Engineering teams with too many doers can't stay on track and spend much of their time in technical disagreements, sidetracks, distractions and misalignment problems. Everyone makes decisions in isolations, and chaos reigns. The resulting software products feel like a collection of features stuck together with no vision and significant integration and usability issues.

Given the need for leaders, it is essential for engineering managers to learn how to spot and coach people into leadership roles.

C<sub>2</sub>A
---

In this article, I am not going to discuss what a leader does. I already wrote about their responsibilities and the most common mistakes they make in a post titled ["11 Top Responsibilities and 10 Common Mistakes of a Technical Leader."](https://www.coderhood.com/11-top-responsibilities-and-10-common-mistakes-of-a-technical-leader/) Instead, I am going to examine how to spot software developers with potential leadership skills, and how to coach them into technical leaders. The topic is vast. In the limited space of this article, I'll just scratch the surface.

First of all, let's examine the three fundamental personality traits that a leader must either have or acquire. A leader must be **calm, confident, and assertive**. Those qualities are as necessary for a leader as water is essential for human life. For this reason, I shorten the Calm + Confident + Assertive formula with **C<sub>2</sub>A**, as a play on H<sub>2</sub>O, the chemicals formula of water.

### C is for Calm

Leaders don't force others to follow them. Those are dictators, and dictators are a different breed that has no place in the software industry. Instead, leaders possess characteristics that induce others to trust and follow them because they choose to do so. One of the requirements for that to happen is for a leader to be calm.

A calm person is composed and does not show nervousness, anger, loss of control or other overwhelming emotions. If a leader is not calm and composed, people will tend to abandon them or not follow them in the first place. Exceptions occur if some other skill makes up for it. We have seen examples of exceptions of this kind in people like Steve Jobs. His lack of composure was made up by his product vision, business insight, and understanding of the customer.

People do not follow an angry or emotional person because such individual cannot be trusted. A person who is not in control cannot direct others, and thus cannot be an effective leader. Note that this does not mean that a leader should never become agitated or show emotion. A leader does not have to be a robot. However, a leader should be calm most of the time.

### C is for Confident

A leader must act with confidence; that is, they must show certainty and determination in their interactions with others. Calm confidence is a powerful magnet that attracts a following and inspires trust.

A confident person does not have all the answers all the time. However, a confident person knows when he or she has a solution with facts and information to back it up. A confident person is also ready to change answer when a better one surfaces.

People do not follow people that lack confidence. It is a demonstration of a weakness of character or knowledge, and it is not a characteristic that inspires trust.

### A is for Assertive

Being assertive is a necessary ingredient of leadership. Leaders who navigate difficult situations must be able to deal with dissent and disagreement. Being assertive allows a leader to break through the waves of chaos, and set a direction for others to follow.

Assertiveness doesn't need to be forceful, aggressive, pushy or loud. Assertiveness can and should be gentle. Together with a calm and confident demeanor, gentle assertiveness is a powerful tool to influence others, gain trust and direct a group in a particular direction.

Assertiveness is also not a characteristic reserved for extroverts. Many introverts are assertive, and their hallmark gentle, calm and confident type of assertiveness makes them strong functional leaders.

A Reminder To Myself
--------------------

Being **C<sub>2</sub>A** is such an important thing for me to remind myself every day that I created the following iPhone lock-screen background.

[![](https://thepracticaldev.s3.amazonaws.com/i/obzxzjje0m2kqc5x95jq.jpg)](https://i1.wp.com/c1.staticflickr.com/5/4573/38315037106_57683e5d68_o_d.jpg?ssl=1)

My iPhone lock-screen background.

If you want to use it feel free to [click on it](https://c1.staticflickr.com/5/4573/38315037106_57683e5d68_o_d.jpg) to download a full-size version to put on your phone. Once it is your lock screen, you'll see it every time you access your phone. Also, feel free to share it in any way you'd like. You have my full permission.

Spotting a Potential Leader
---------------------------

![](https://thepracticaldev.s3.amazonaws.com/i/xq0rrpb3djwboaayhh8i.jpg)You can spot a potential leader by noticing certain patterns. A potential leader is someone who:

1.  Naturally possesses one or more of the three fundamental characters traits of a leader: calm, confident, assertive (C<sub>2</sub>A)
2.  Is engaged and sees achievements through the prism of company growth.
3.  Is a catalyst who make things happen, as opposed to being a watcher and just observe.
4.  Others listen to them when they speak, and take their word seriously (this is often a natural side effect of C<sub>2</sub>A).
5.  Takes full responsibility for their decisions and never blame others.
6.  Can function and make decisions in situations where there is not enough information.
7.  Can operate and stay productive even in conditions that cause a lot of context switching.
8.  Displays empathy and [emotional intelligence](https://www.coderhood.com/11-best-ways-to-improve-your-emotional-intelligence/) toward others.
9.  Has excellent communication skills.
10. Can influence others.

Coaching a Potential Leader
---------------------------

![](https://thepracticaldev.s3.amazonaws.com/i/qhiq1mw8ybvltzpc7ciy.jpg)

When you see someone who displays at least a few of the ten patterns described above, coaching them to be a leader should start from helping them learn to be calm, confident and assertive.

Eventually, a leader needs to master each of the patterns. However, if they get the first one, the rest will tend to come more easily.

Here are other things you can do to coach them:

1.  Let them know that you see a leadership spark in them. If they are interested in becoming leaders, make sure they want your help. You should never attempt to coach somebody without telling them exactly what your intentions are. It is important that they work with you deliberately.
2.  "Leadership," in many software engineers' minds, sounds like a buzzword. You should ensure that it is well defined and characterized. Talk to them about the [responsibilities of a technical leader,](https://www.coderhood.com/11-top-responsibilities-and-10-common-mistakes-of-a-technical-leader/) and don't make them guess what you mean by "leader."
3.  Help them understand that success for leaders is measured through their ability to help the company grow; this is a big point of view switch for some people so it might take some time to sink in fully. An engineer is often measured by the quality and velocity of their output, while a leader is measured by the impact of other people's output.
4.  Help them understand that leadership is a game that requires active participation. They can't just sit and watch. Leaders carry the ball and get bruised in the process, if necessary. They also watch out for their people, protecting them from getting bruised too often.
5.  Help them understand that leaders are entirely responsible and accountable for the results that their people achieve, and the mistakes they make. At the same time, leaders must be maniacal about giving full credit to their people for excellent results they deliver.
6.  Help them realize that there is never enough information to make perfect decisions. Leaders must be able to use the information that is available and determine a course of action. Always waiting to have more data results in paralysis, and it is not a desirable or acceptable behavior for a leader.
7.  Help them accept that interruptions are a fact of life for a leader, and they need to become pretty good at dealing with it while remaining productive.
8.  Leaders must display empathy and work on improving their [emotional intelligence](https://www.coderhood.com/11-best-ways-to-improve-your-emotional-intelligence/); this is an area where a coach can help by pointing out issues. An important point distinction here: someone who simply lacks empathy cannot be coached in any reasonable timeframe. However, someone who has empathy but fails to display it can be coached to open up.
9.  Help them with their communication skills, by pointing out problems in that area when you see it; this is a sticking point for many people. I have seen countless potentially good leaders not able to leap to leadership because they were unable to communicate clearly.
10. Results ultimately measure success. Help a potential leader know that they are expected to learn how to influence others.

Final Thoughts
--------------

Helping somebody grow into a leader is an art form that requires time and focus. However, when you are working with the right people, the satisfaction of growing their skills pays off for itself.  If in the process you feel like you are teaching somebody to do your job, you are on the right path. In fact, to progress, you need to [coach someone to take your job](https://www.coderhood.com/career-advice-work-yourself-out-of-your-job/).

---

### If you enjoyed this article, keep in touch!

- [Find all my posts on CoderHood. Don't forget to Subscribe to receive notifications of new posts by Email.](http://www.coderhood.com) 
- [Join my professional network on LinkedIn.](https://www.linkedin.com/in/lpasqualis/)
- [Follow me on Twitter.](https://twitter.com/lpasqualis)
- [Join my Facebook page.](https://www.facebook.com/coderhood/)
- And finally, follow me here on dev.to!