Three things we notice when capability actually changes

The signs that matter are easy to miss

Most organisations measure leadership development by the wrong things. They count training hours logged, survey satisfaction scores, and note whether leaders can describe the model they were taught. None of that tells you whether capability has actually changed.

The trouble is that genuine change in a leader is subtle, at least at first. It does not announce itself with a new vocabulary or a more assertive presence. It tends to show up in the texture of ordinary moments: how someone handles a difficult question in a meeting, what they do with an unexpected setback, how they take responsibility when something goes wrong. These are the moments that reveal what has actually shifted, and they are easy to overlook if you are not watching for them.

This matters practically. If you are responsible for leadership development in your organisation, and you have invested time, money, and credibility in a programme, you need to know whether it is doing anything real. And if you are a leader in development yourself, you deserve a more honest account of what progress actually looks like than "you seem more confident" or "people say you've changed."

What follows is a field note. These are the three markers we observe most reliably when a leader's capability is genuinely developing. They are drawn from direct work alongside leaders over time, not from a single intervention or a before-and-after survey. Each one has a recognisable pattern, a recognisable failure mode, and a recognisable moment when it starts to shift.

Marker one: they become harder to rattle

Early in their development, most leaders manage pressure by tightening. They work longer hours, take more decisions themselves, narrow the scope of what they pay attention to, and keep a tighter grip on information. This is a coherent, if costly, strategy: when you feel threatened by circumstances, you reduce the surface area of threat. The problem is that it makes you less effective, not more. And it signals to the people around you that pressure is dangerous, that the right response is to contract.

As capability develops, something loosens. The external pressure does not go away. In fact, some leaders we work with are carrying more responsibility than they were at the start of the engagement. But their relationship to that pressure changes. They stay present in situations that previously triggered a defensive response. They can hold a tense conversation without needing to end it quickly. They can receive difficult feedback without either deflecting it or collapsing under it. They can sit with a problem that does not have an obvious answer, and remain functional.

This is not indifference. It is not a performance of calm. It is something more substantial: a leader who has become more settled in themselves, more secure in their sense of who they are and what they stand for, is genuinely less destabilised by external turbulence. The noise is still there. They just carry it differently.

A pattern we observe. A financial services executive we worked with over eighteen months had a reputation for becoming visibly combative under pressure. In early sessions, she described this as "not suffering fools," but what she was actually doing was shutting down uncertainty. Any ambiguity in a conversation read, at some level, as threat. Over time, as the inside-out work progressed, something measurable changed. Colleagues began bringing her problems they had previously routed around her. Her team's willingness to escalate difficult issues increased. She had not softened, exactly. She had become more solid. That solidity made her accessible in a way that her earlier intensity never had.

This is one reason we place so much emphasis on the inner work in the DUAL model. The D (Discover) and U (Understand) stages are not warm-up exercises for the "real" development. They are the foundation that makes this kind of steadiness possible. Without that inner grounding, pressure-management stays at the level of technique: breathing exercises, scripted responses, deliberate pauses. With it, the change is structural.

Marker two: they start asking different questions

The questions a leader asks are a precise diagnostic. Not what they say in a presentation or how they describe their leadership philosophy, but the actual questions they put to people in real conversations. These are hard to fake and hard to maintain under pressure, which makes them unusually reliable as a signal.

Less capable leaders ask instrumental questions. They ask questions to gather information they need in order to act. The question is a mechanism for reducing uncertainty, and it closes once the information is obtained. There is nothing wrong with this in narrow contexts. But when it becomes the only mode, it signals a leader who is oriented primarily towards their own understanding and their own next move.

More capable leaders ask questions they do not already know the answer to. They ask because they are genuinely curious about how someone else sees the problem. They ask and then stay with what they hear, even if it complicates their existing view. They can hold a question open in a meeting without rushing to resolve it. They can hear a disagreement and stay interested in it rather than immediately trying to adjudicate it.

This shows up in ways that are visible to everyone in the room. A leader who is asking to understand runs a different kind of meeting from a leader who is asking to confirm. The first creates space for the people with the most relevant knowledge to contribute it. The second creates a room full of people calibrating their answers to what the leader seems to want to hear.

A pattern we observe. A regional operations director in a retail group was known for running efficient meetings. Decisions were made quickly; action items were clear. What was less visible was that his teams had stopped surfacing problems early. By the time issues reached him, they had already been shaped and smoothed by several layers of informal management. The early warning signals he needed were being filtered out before they arrived. About a year into the capability work, his direct reports began to notice a change: he was asking them what they thought, then visibly thinking about what they said before responding. He was not agreeing with everything; he was genuinely considering it. Within six months, the quality of information reaching him had improved substantially, and the team's collective ability to manage emerging problems had improved alongside it.

This kind of shift connects directly to the research on inside-out development. A leader's capacity to stay genuinely curious under pressure is not a skill that can be installed by a workshop on active listening. It requires a prior shift in how secure that leader is in their own perspective: when you are not anxious about having the right answer, you can afford to be interested in someone else's.

Marker three: they take responsibility without drama

This is the marker that takes the longest to develop, and the one that is most diagnostic of genuine capability when it appears.

Every organisation has a working theory of how leaders should handle mistakes. Some organisations reward speed of recovery: name the problem, assign accountability, move on. Others are more forgiving of the mistake itself but expect visible contrition. What most organisations get, in practice, is a mixture of two dysfunctional patterns. Neither is the thing we are looking for.

The first failure mode is defensiveness. The leader who is defensive about their mistakes is managing their reputation rather than addressing reality. They may acknowledge that something went wrong, but the acknowledgement is partial, hedged, or accompanied by an account of why the situation made the mistake nearly inevitable. The subtext is: this was not really my fault, or at least not my fault alone. People around this leader learn not to bring problems, because the problems will come back to them.

The second failure mode is theatrical self-blame. This pattern is more subtle and, in some organisational cultures, more accepted. The leader who over-apologises, who describes themselves as having "completely let the team down," who makes the mistake the centrepiece of a narrative about their own inadequacy, is also managing their reputation. They are just doing it by pre-empting judgement. The effect on the team is different but not better: it creates awkwardness, absorbs energy, and shifts the focus from what went wrong and what to do about it to managing the leader's emotional state.

Mature responsibility looks different from both of these. It is plain. The leader names what went wrong, owns their part in it without qualification or performance, says what they learnt from it, says what will change, and moves on. The whole transaction is fast, clean, and proportionate. It does not invite the team into an appraisal of the leader's character; it addresses the situation.

A pattern we observe. A general manager in a logistics company had a strong results orientation and a record of delivery. What his team consistently reported in 360 feedback was that he was "difficult to talk to when things went wrong." Working through what this meant in practice, it became clear that his default was the theatrical self-blame pattern: when a client escalation occurred on his watch, he would hold a lengthy debrief in which he described his own failures in considerable detail. His intention was transparency. The effect was that his team spent the debrief reassuring him rather than learning from the incident. Over the course of the capability work, this changed. His debriefs became shorter and more useful. He named the facts, owned the relevant decisions, identified what would change, and moved on. His team began describing him differently in subsequent feedback rounds: as "direct," "clear," and "easy to work with when things go wrong." His actual performance had not changed dramatically. His team's willingness to bring him real information had.

This is why accountability is a capability question, not a character question. The leader who has developed genuinely is not more virtuous than the defensive leader or the theatrical one. They are less anxious. Their identity is not at stake in the same way when something goes wrong, so they can respond to the situation rather than managing their exposure.

What these markers mean for how you measure development

The three markers described here share a structural feature: they are all evidence of something shifting at the identity level, not just the skill level. A leader who has become harder to rattle has not learnt a new technique for managing stress; they have become more settled in who they are. A leader who asks genuinely curious questions has not memorised a list of open questions; they have become less anxious about being wrong. A leader who takes responsibility without drama has not been coached on the language of accountability; they have become less dependent on the protection of their reputation.

This is what distinguishes capability from competency. Competency is the ability to perform a specific behaviour in a context where the behaviour is required. Capability is something more robust: it is the capacity to act well across a range of contexts, including contexts that are ambiguous, pressured, or novel. Competency can be trained. Capability, as the research on lasting change consistently shows, has to be built from the inside out.

This has implications for how development is designed and how it is measured. If you are tracking whether leaders can describe a model, you are measuring comprehension. If you are tracking whether leaders demonstrate specific behaviours in a controlled context, you are measuring performance. If you want to know whether capability has actually changed, you need to watch how a leader behaves in moments that were not anticipated and not rehearsed. You need to be close enough to the work to see the texture of ordinary interactions, not just the high-stakes moments that get reported upward.

The markers described here are not a formal instrument or a validated scale. They are observational anchors: things we have learnt to watch for because they reliably show up when genuine development is happening, and reliably stay absent when it is not. They are a starting point for a more honest conversation about what leadership development is actually producing.

For those interested in how CapabilityFX builds these conditions systematically, the DUAL model describes the four stages through which this kind of inside-out development is structured. And if the question of how your current approach measures up is live for you, our services page describes the different ways we work alongside leaders and organisations.

If you want to talk through what genuine development could look like in your context, we are happy to have that conversation. Reach out via the contact page.

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