Leadership capability at every level is what lets an organisation keep performing when it grows, changes or adopts new technology, and it has to be built on purpose. I spoke with Dr. RK Prasad, CEO of CommLab India, on episode 79 of The eLearning Champion Podcast about exactly that. This article sets out my position on the main themes we covered, so you can read the argument first and then watch the conversation.
The themes were leadership versus management, emotional intelligence, the circle of control, capability architecture, capability pathways, and what happens to leadership and culture when AI arrives. They look like separate topics. I treat them as one question: how does an organisation produce capable leaders on purpose, at every layer, instead of hoping a few talented people carry the rest?
Why does leadership capability at every level matter?
Most organisations still treat leadership development as something kept for senior executives. The assumption is that capability sits at the top and flows down through instructions. I see the opposite. Performance is decided by thousands of small decisions made by people who are rarely in the boardroom: a team leader choosing how to handle a missed deadline, a manager deciding whether to raise a concern, a project lead settling a dispute between two functions.
If those people have not been given the judgement, the authority and the habits to lead well, the strategy at the top never arrives intact. It gets diluted at every handoff. That is why I describe leadership capability at every level as a structural requirement. It is not a perk for high-potential staff, and it is not a reward for seniority.
Capability that exists only at the top is also a single point of failure. In a growing company that small group is always stretched, and when it is full the rest of the organisation has nowhere to turn. I have written about the mechanism in why leadership capability does not scale with company growth. Growth adds complexity to every leader's job faster than anything adds judgement to the person doing it, and the gap shows up first in the layers furthest from the top.
Why an organisation needs both leadership and management
Leadership is not a job title. That sentence sounds obvious and is routinely ignored, because most organisations still give leadership responsibility to whoever holds a management role, and then wonder why the two get confused. Management is the work of coordinating tasks, people and resources so that things are delivered. Leadership is the work of setting direction, building the conditions people need, and carrying a group through change.
An organisation needs both, and it can fail by overinvesting in either. Promote people into management roles without building their leadership capability and you get well-organised teams that do not know where they are going. Celebrate leadership and neglect management and you get a compelling direction with nothing reliable underneath it. The two sit in the same person at most levels, which is why the ability to work effectively with people sits at the centre of leadership capability.
The layer most likely to be missed is the middle. Managers there translate strategy into daily work, and they are rarely given the capability to do it. My view on that is in why middle managers are the missing layer in transformation delivery.
Emotional intelligence and the circle of control
Two ideas in the conversation sit close together, emotional intelligence and the circle of control, and both are practical. Emotional intelligence is the ability to notice your own reactions, read other people accurately, and adjust what you do as a result. In leadership it decides whether a difficult message lands or a team goes quiet. I cover it in more depth in mastering emotional intelligence in leadership.
The circle of control is a sorting tool. Draw three zones: what you control directly, what you can influence but not command, and what you can do nothing about. A leader who spends energy in the third zone burns credibility and wears out the team. A leader who works the first two zones deliberately becomes steadier, and the team learns where effort pays off.
Used together, they give a leader a simple routine under pressure. First, notice the reaction. Then ask which zone the problem sits in. Then act on the part that is theirs. It is not complicated, and that is the point: it can be taught to a first-time team leader, and it is just as useful to a chief executive.
What does leadership capability architecture mean in practice?
Leadership Capability Architecture™ is the design of the decision rights, expectations, pathways and routines that let an organisation produce capable leaders on purpose. It is a structure. A training programme, a competency list or a curriculum with a new name on the cover is not one. I developed it because leadership is so often trained and coached and so rarely designed. The full account is in the comprehensive guide to leadership capability architecture.
The difference shows up the first time the budget shrinks. A development programme builds skills in individuals, and when it stops the skills fade. An architecture builds capacity into the organisation, so it keeps working through a reorganisation, a change of chief executive or a hiring freeze. That is why I put the work in the system leaders operate in, and designed before anyone is trained.
It also changes what you do on a Monday morning. You stop scheduling workshops first. You start by asking which capabilities the strategy actually requires, who needs them, and what has to be true in the organisation for those people to use them. Capacity and capability are different things, a distinction I set out in leadership capacity versus capability, and an architecture is aimed at capability.
How capability pathways support development at scale
A capability pathway is a visible route from one level of leadership to the next. It says what a person at each level is expected to be able to do, what they need to demonstrate before moving on, and how the organisation will help them get there. Without it, development depends on who your manager happens to be.
Pathways matter most at scale because scale removes the informal ways people used to learn. In a small company you absorb leadership by watching the founder. In a large one there is no single person to watch, and different business units set different standards without anyone deciding to. A pathway makes the standard explicit and shared. I take that problem on directly in how you build leadership capability across business units.
A pathway also serves the individual. People can see what is expected, what is next, and why a particular development step matters. That visibility is a large part of why people stay and grow, and it is what turns development from an event into something an organisation can count on.
Reinforcing capability and culture as organisations adopt AI
The host raised a point near the end of the conversation that I would underline: capability and culture have to be reinforced as organisations grow, transform and adopt AI. New tools arrive faster than new habits. If the habits, expectations and decision rights around a tool are not designed, people use it in the way that is easiest, and the organisation drifts.
Reinforcement is the part most programmes skip. A workshop can introduce an idea in a day. Culture changes through what leaders do every week, what gets noticed, and what the structure rewards. My view is that culture works as infrastructure, which I describe in culture as leadership infrastructure, and that the managers closest to daily work decide whether new tools stick. I cover that in how middle managers make AI adoption work.
The last chapters of the conversation turn to AI and leadership and to building a digital twin. That part is better heard than paraphrased, so I will leave it to the recording. If you want to see where my own work on AI and leadership stands, the CapabilityAI page is the place to look.
What L&D leaders can take from the conversation
If you lead learning and development, run training, design instruction or hold a people role in the business, these are the points I would act on first.
- Decide which levels carry the load: List the levels where decisions that matter are made and ask whether the people there have the capability and authority to make them. Start where the gap is widest, not where the budget is easiest.
- Treat leadership and management as two jobs: Name what you expect of each at every level. If you cannot say which parts of a role are leadership and which are management, nobody else can either.
- Give people a routine for pressure: Teach a simple sequence, such as notice the reaction, sort the problem by control, act on your part. A small habit used often beats a large framework used once.
- Build pathways before programmes: Define what good looks like at each level and how someone moves up. Then choose the development that gets them there.
- Plan the reinforcement: Decide in advance how new capability will be noticed, supported and rewarded after the programme ends, and who owns that. Build it into the design, not the follow-up.
Watch the conversation
The full episode runs for 55 minutes. You can watch it on the media page of this site, and CommLab India hosts the series on its own podcast page. The chapters are:
- 03:07: Leadership vs. Management
- 07:33: Emotional Intelligence and the Circle of Control
- 08:17: The Circle of Control
- 13:07: The Five Cs of an Effective Leader
- 18:20: Capability Architecture
- 35:15: Capability Pathways
- 47:04: AI and Leadership
- 47:47: Building a Digital Twin
I have written about my own Five Cs in the five Cs of effective leadership in a hybrid world.
If you want to see where leadership capability is thin in your own organisation, the leadership assessments are the starting point. If you would rather talk it through, working with me explains how I engage with leadership teams.