How to Close the Gap Between Knowing and Doing: The Capability Practice Method.

There is a man called Martin Ward who, for most of his adult life, was told he would never run.

Two collapsed lungs, a slipped disc, registered disabled in his thirties. Back at school, his PE teacher told him he was rubbish at sport, and he believed it, and carried that story about himself for decades.

Then, in his mid-fifties, he watched his son finish a half marathon along the Welsh coastline, and he turned to his wife and said he would love to do that.

He started the way anyone sensible would start from zero, not with a training plan, not with a race entry, but by jogging between lamp posts. One lamp post to the next, then around the block, then to his allotment, then a parkrun, then a 3k, then a 10k. Only at some point later, he bought his first pair of running shoes.

By the age of sixty-four, Martin Ward had completed one hundred marathons and become the oldest person in the UK to do that.

What made the difference was not a revelation about running, and it was not grit alone. What made the difference was a process, lamp post by lamp post, building a capability he was told he did not have, from the smallest possible starting point, through patient and deliberate repetition, over years.

We understand this instinctively when it comes to physical skills. Nobody watches someone perform a difficult gymnastics routine and assumes she got there by reading a really good book about balance. We accept this completely in sport or art, we do not expect a beginner to nail the most complex skill on their first attempt, we expect them to build, carefully and incrementally, the underlying capabilities that will eventually make it possible.

When it comes to leading people, though, we seem to expect something entirely different.

Every year, millions of managers attend leadership development programmes. They read the books, they sit in workshops about psychological safety, strategic thinking, executive presence, and how to have difficult conversations. They learn frameworks, they discuss case studies, they leave with good intentions.

And then they go back to work, and almost nothing changes.

• You know that delegating properly means letting go of control. And yet you still find yourself doing the thing yourself, because it is faster, because the deadline is tomorrow, because you are not quite sure they will get it right.

• You know that being more visible to senior stakeholders means speaking up, building relationships before you need them. And yet something consistently stops you, it feels self-promotional, uncomfortable, not really who you are.

• You know that giving honest feedback early is kinder and more effective than waiting until things become a problem. And still the conversation gets postponed, softened, eventually abandoned.

The gap between knowing and doing is persistent and has nothing to do with intelligence or motivation. Something more structural is going on, and understanding what it is changes everything about how we approach development.

I have built a free practice guide for the capability managers struggle with most, influencing stakeholders. With practices you can adapt to your own situation. Download here.

The knowing-doing gap has roots in three distinct places, and each one explains a different reason why insight alone so rarely leads to lasting change.

The psychological layer. Robert Kegan and Lisa Lahey, in their research on immunity to change, found something counterintuitive: beneath every sincere intention to change, there is often a competing commitment, a hidden assumption about what would happen if the change actually occurred. It means that understanding the concept of delegation does nothing to loosen the grip of the underlying belief (“I mustn’t lose control”). The insight lands on the surface, the deeper structure continues sabotaging you.

The neurological layer. Behaviour is not stored in the brain as ideas, it is encoded as patterns, neural pathways built through repetition and activated automatically in familiar situations. When you walk into a difficult conversation, your brain does not pause to consult your notes from the last leadership training, it runs the pattern it knows. That pattern has been practised thousands of times and is fast and largely unconscious. Building a new behavioural pattern requires new neural pathways to be established, and that happens only through repeated practice in real conditions. The insight from the workshop fades within weeks precisely because it was never encoded where behaviour actually lives.

The social layer. We do not develop in isolation. The manager who returns from a programme with genuine intentions to lead differently walks back into a team that has learned to expect a certain version of them, a culture with its own unwritten rules about what is rewarded, and a calendar that leaves no space for anything deliberate. The environment does not adapt to the new insight, it continues to reinforce the old patterns, and the path of least resistance is always the familiar behaviour.

None of this is destiny. But it does mean that knowledge transfer is not the same as capability development, and until we treat them differently, the gap remains.

So if knowing is not enough, what is?

This is where we return to Martin Ward between his lamp posts, and to every person who has ever built a physical skill through patient, incremental, deliberate practice.

The principle is not new. Anders Ericsson spent decades studying expert performers across domains and found that what separated the exceptional from the merely competent was not talent, and not effort in the generic sense, but a specific kind of practice, deliberate, focused on the right things, sustained over time with feedback and repetition. The skill was built from the bottom up, assembled from its component parts.

What the Leadership Capabilities System is built on is the argument that leadership works exactly the same way. It is not a set of traits you either have or develop through inspiration, it is a craft, built through practice.

The method has three levels.

At the broadest level, there are capabilities, the meaningful leadership qualities that organisations ask for and development programmes attempt to build. Strategic thinking, influencing stakeholders, developing people. These are far too large to practise directly, in the same way that telling someone to be a better dancer is not a useful instruction if they have never learned to balance properly.

Beneath each capability sit competencies, the distinct skill clusters that together compose it. Influencing stakeholders, for example, is not one thing, it requires understanding what different people care about and why, it requires building relationships consistently rather than only when you need something. Each of these is learnable, separable, and something that different people will be stronger or weaker in, just as different athletes need to work on different physical foundations.

At the most specific level are practices, concrete, repeatable, small behavioural moves that build the competency through consistent repetition. Not principles to internalise, but things to actually do. Specific enough to try in a real situation tomorrow, simple enough to sustain under pressure, targeted enough to build the right neural pathway, one repetition at a time.

This is the lamp-post principle applied to leadership. You do not start by becoming a strategic influencer, you start with the smallest move that builds the right capability, in the right direction, and you do it until it is no longer effortful. Then you add the next one.

Knowing that you need to practice is not the same as building it. To approach practice effectively, we can break it down into three levels:

Notice. Before you change anything, you train your observation muscle. Premature action, before you have real data about your own patterns, produces surface changes that do not hold.

Experiment. Once you can see the pattern clearly, you form a hypothesis about one part of it, and you design one small action around it. You run it for two to three weeks and you observe what shifts. The experiment is designed by you for your specific situation.

Integrate. The practice stops feeling like a practice and starts becoming part of how you lead, including under pressure. You know you are there when you are doing it when it is hard, not just when it is easy.

Move through these at your own pace. Two weeks of noticing is not too long, and if you rush to experiment before you have genuinely seen your pattern, you will be practising the wrong thing, carefully, which is its own kind of waste.

Start with one capability and one practice.

I have prepared a full Capability Practice Guide for one of the capabilities mid-level leaders find most painful, influencing stakeholders. The guide takes you through all three phases, Notice, Experiment, and Integrate, with specific practices to adapt to your own situation.

It is free for subscribers, instant download. If you are not yet subscribed, adding your email to the form is enough to get it.

👉Free Practice Building Guide: Influencing Stakeholders→

Not sure which capability to prioritise? The Leadership Capability Snapshot maps your strengths across all nine in about ten minutes, and points you to the one most worth your attention now.

Take the Leadership Capability Snapshot →

The lamp post is right there. The question is only whether you start, and whether you come back and do it again.

This article introduces the foundation of the Leadership Capabilities System, the framework that underlies everything on this blog. Each post translates a leadership concept into specific capabilities, competencies, and practices, so that development moves from the page into the work itself.