Why your leadership programme is not building capability

Ask an L&D director how last year's leadership programme went, and you will usually get a measured answer. Participant feedback was strong. The facilitator was sharp. The content was well-designed. Ask the same director what changed in the business six months later, and the answer gets quieter. The same conversations are still happening. The same decisions are still landing at the same desks. The investment was real; the return is hard to point to.

This is not a facilitator problem. It is not a content problem. It is not even, primarily, a budget problem. It is a design problem rooted in a flawed assumption: that developing a leader means improving what a leader does, when the more durable question is who a leader is becoming.

The competency trap and why it persists

Competency frameworks are the default architecture for most leadership programmes, and it is not hard to see why. They are visible, teachable, and measurable. Define the behaviours that characterise good leadership in this organisation, build learning experiences that close the gap to the model, and measure whether the behaviours change. The logic is clean and defensible to a budget committee.

The problem is that competency describes performance; it does not explain it. A competency framework tells you what good leadership looks like from the outside. It says nothing about what produces it from the inside. And when development is designed around the description rather than the explanation, you train toward the surface and leave the substrate untouched.

This distinction is not academic. Think of a specific observable behaviour: a leader asks better questions in meetings. You can teach the technique, observe how often they use it, track frequency over a quarter. What you cannot read from any of that is whether the leader has become genuinely curious. Curiosity is the capability under the behaviour. Technique without it is mimicry, and mimicry stops performing the moment conditions change, the moment a meeting turns adversarial or the question threatens a comfortable assumption. The behaviour may persist for a while on the strength of effort and goodwill. It rarely persists when effort is scarce, which is exactly when it is most needed.

Organisations invest in the visible layer because it is where training tools work best and where reporting is cleanest. The underlying condition, the one that actually decides whether the behaviour holds, is harder to build and harder to measure. Most programmes never try.

Why frameworks feel like progress

There is a second, quieter reason competency frameworks persist: they feel like progress. Defining good leadership is valuable work. Getting senior stakeholders to agree on a shared model creates real alignment. Running a 360-degree feedback cycle gives people an honest picture of how they are perceived. None of that is wrong. The problem comes at the next step, when the organisation concludes that the gap between current behaviour and the model is a training gap, solvable with better input. It is usually a development gap, meaning it requires the leader to grow, not just to learn. Training and development are not interchangeable, and conflating them is where the investment starts to leak.

What capability actually is

Capability is not a skill. A skill is specific and transferable: structuring a difficult conversation, reading a profit-and-loss account, facilitating a planning session. Skills can be taught, practised, and assessed. They are real and they matter, and CapabilityFX does not argue against building them. The argument is about where the real gains come from.

Capability is the internal condition from which skilled behaviour flows. A capable leader brings a way of being to a situation, a quality of judgement and a clarity about what they stand for, that shapes how any given skill is deployed. When a capable leader runs a difficult conversation, the technique matters less than the fact that they are genuinely willing to hear something uncomfortable and to hold steady if they do. That willingness is not a skill you can teach in a module. It is a property of who the person is at that moment, what they believe about themselves and about what leadership requires of them.

The DUAL model, which organises how we think about leadership development at CapabilityFX, describes this movement from the inside out. Discover: the leader sees clearly what is actually happening, without the distortion of self-protection. Understand: they make sense of it with honesty, not with the narrative that is most comfortable. Accept: they hold the reality, including the uncomfortable parts, before they act. Lead: they act from that grounded place. The sequence matters because each stage is a capability in itself. A leader who can Discover and Understand but not Accept, who arrives at an honest picture and then retreats from it, will still make the decisions their blind spots permit. No amount of skills training addresses that. The work has to happen at the Accept stage, and that is inside-out work.

The conditions that development requires

Identity-level development is slow, less visible, and harder to measure than skills development. This is not a weakness of the model; it is the nature of the thing. Who a person is does not change in a two-day programme. It changes through sustained challenge, honest reflection, and the accumulated experience of being held accountable to a higher standard over time. What organisations typically create are conditions designed for the opposite: time-compressed, high-stimulus, back-to-the-same-pressures-on-Monday.

This matters structurally. A leader who spends two days interrogating their assumptions about authority, about what it means to not know, about how they use positional power, and then returns to an environment that does not support or reinforce any of that, will default. The development evaporates, not because it was poorly designed but because the environment was not redesigned alongside it. Lasting capability needs three things that most programmes do not provide in adequate measure.

Duration. Not more days of input, but a longer arc of practice, reflection, and challenge spread across months. Capability is built by encountering difficulty, responding, reflecting on the response, and encountering difficulty again. That cycle does not complete in a single cohort run.

Intimacy. Smaller groups allow leaders to be genuinely known and genuinely challenged. Large cohorts create the conditions for performance and concealment. A leader can sit through three days of development in a group of 30 and never have their actual assumptions examined. In a group of eight, working over six months, that is much harder to sustain, and the inability to conceal is where the real work begins.

Accountability structures. Development that disappears into the busyness of the organisation after each session builds nothing durable. The most effective programmes build in structured return: what did you try, what did you notice, what did you avoid, and why. Not as a reporting mechanism but as the practice of honest examination, repeated until it becomes the leader's own habit.

Our 4D method works within this architecture: the engagement is designed to hold all three conditions across the arc of the programme, not to simulate them in a compressed sprint.

What it looks like in practice

The gap between competency and capability is most visible in specific leaders doing specific work.

The operations executive with high scores and low presence. A regional operations executive in a mid-sized manufacturing business had completed two leadership programmes in as many years. Both were well-regarded. Both had returned strong feedback scores. Her 360-degree profile showed she had closed the gaps the first programme identified. On paper, the development was working. In the room, something was different. When her team raised concerns about a supplier relationship, she managed the conversation efficiently but ended it before anyone had said anything genuinely risky. She answered every question except the one she could hear coming. Her competency was intact. Her capability to hold a conversation that threatened her preferred version of events had not been examined, because neither programme had ever required her to do so. The gap was not visible in her scores. It was visible in the room she created around her.

The finance director who needed to change, not learn. A finance director at a professional services firm was told he needed to "develop his influence." Two programmes and a coaching engagement later, the feedback was the same. He had learned the language of influence. He had practised the techniques. He could articulate the principles in a conversation about leadership. What he had not examined was his genuine discomfort with the idea that persuading people was a legitimate form of leadership. He believed, at some level he had never been asked to look at directly, that good decisions should be self-evident and that a leader who needed to advocate for them was compensating for their quality. No module addresses that. That is a belief about what leadership is, and until it shifts, every influence technique sits on top of a foundation that undermines it. The skills could not do the work because the identity had not moved.

What connects both cases is the same thing: well-designed programmes producing capable-looking outputs and not producing lasting capability. The leaders were not unserious. The programmes were not poor. The design assumption was wrong.

What HR and L&D directors should change

If the above lands as a diagnosis, the question is what to do with it. Three shifts are within reach without requiring a complete redesign of every programme.

Stop measuring only outputs and start asking what changed inside. Post-programme surveys measure satisfaction and immediate reaction. More useful, six months later, is whether the leader is asking different questions of themselves: whether they are holding difficult conversations they would previously have deferred, whether they are visible in moments of uncertainty or still absent from them. These are behavioural signals of identity movement. They are harder to score, and they are what actually matters.

Design for return, not just attendance. A programme that runs as a series of sessions spread across four to six months, with structured reflection between each, will do more developmental work than the same hours compressed into two days. The compression is often driven by cost and convenience, not by what development requires. The business case for spreading the arc is the business case for the investment working.

Match the programme to the actual question. If the question is skills, train for skills. If the question is who these leaders need to become to meet the demands in front of the organisation, that requires a different conversation. Our services are designed around the second question, which is the one most organisations are actually trying to answer without quite saying so. If you want to understand where your leadership population sits on the capability dimensions that predict performance under pressure, our assessments page sets out what we use and why.

The leaders who shift an organisation shift themselves first

There is a short version of everything in this article. The organisations whose leadership investment produces lasting returns have, without exception, created the conditions for their leaders to grow at the level of identity, not only at the level of skill. They do not do this because it is philosophically interesting. They do it because they have tried the alternative, measured the result honestly, and found that it does not hold.

The investment required is real: more time, smaller groups, more honest conversations about what development actually demands. So is the return. If you want to understand what that looks like for your own leadership population, start a conversation with us.

The leaders described here are representative composites drawn from patterns we observe in practice, not identifiable individuals.