Skills Are Teachable. Capability Is Built.

A leader can know the model and still avoid the moment that matters. That is not always a skills gap. It is the difference between having a skill and being capable when the pressure is on.

You have seen it too. A leader who can explain the strategy framework but cannot connect it to the market. Someone who appears to have every skill the next role demands, yet still cannot step into it.

And, more personally, I know the feedback model by heart. I even teach it to others. Still, in some moments, I avoid the difficult conversation.

For a long time, I read examples like these as gaps in skill. Increasingly, I think they point to a confusion at the center of how we develop people. It starts with the word we lean on most.

Skill is one part of what capability holds

A skill is something a person can do: read a balance sheet, run a coaching conversation, or plan a project. It is real, useful and teachable.

Capability is the container around it. It holds the skill, and with it the knowledge, judgment, character and reflection a real situation asks for. It becomes visible when the pressure is on and there is no model in front of you to follow.

A manager may know a feedback model and still avoid the conversation. A leader may understand a strategy framework and still fail to connect it to the market. A high-potential employee may have the individual skills for the next role and still not be ready to hold it.

Skill is what someone can do. Capability is what still shows up when it counts.

Head, hands, heart and heels

At Relevance, we use four dimensions to make capability practical. They help us see why knowledge matters, but is never the whole story.

Head is the easiest dimension to teach. The other three develop through practice, feedback, reflection and real experience. They are also shaped by the people around the learner.

Content can help someone understand a difficult conversation. Capability is built when they rehearse it, receive honest feedback, reflect on what happened and eventually have the real conversation.

Where skills-based work often stops

Skills-based work gives organizations a useful language. It can name the competencies a strategy requires and make gaps visible. That is valuable.

But it stalls when naming the skill becomes the whole job. The organization defines a competency, measures the distance and assigns content to close it. What is missing is the translation from a label into the practice that makes the capability real.

Capability also grows faster when development starts from what someone already does well. A gap shows where attention is needed. A strength provides the footing for harder work. Development is not merely gap closure; it is partly an identity project. People are trying out who they can become.

The label is the easy part. The real design question is: what combination of motivation, practice, feedback, reflection and support will make this capability available in a moment that matters?

A training event is only one input

The research on learning transfer has been consistent for decades: what happens around the learning event matters at least as much as the event itself.

Before the program, people need to understand why the development matters to their work. Choice, relevance, visible progress and support from a manager affect whether they enter with the intention to apply what they learn.

During the program, people need more than explanation. They need to try, make mistakes, receive feedback and see progress. Memorable learning often includes three things: a genuine surprise, something the learner does rather than only watches, and a moment with real stakes.

After the program, the work continues. A manager asks what the learner will apply. A peer notices new behavior. A facilitator helps make sense of a difficult attempt. The learner reflects, adjusts and tries again.

A memorable experience is not entertainment added to content. It is an experience designed so that the learning keeps resurfacing when the learner needs it.

Capability travels through people

Facilitators and coaches create the safety and challenge that make honest practice possible. Managers connect the learning to real work. Leaders decide whether curiosity, experimentation and reflection are treated as productive work or as distractions from it.

A manager is often the difference between a good program and a changed way of working. Treat a course as a box to tick and people give it the attention a box deserves. Turn it into a conversation about the work, and the learning has somewhere to land.

Measure readiness, not only completion

Completion tells us that someone attended or finished. It does not tell us whether they are ready.

A stronger approach starts from the business outcome and works backwards. Name two or three relevant business measures before design begins, take a baseline, and then review them after capability evidence appears. That review may be a quarter or two later.

A coaching program might connect to the quality of one-to-ones, engagement, retention or internal mobility. Leadership development might connect to planning quality or decision speed. Safety development might connect to reporting culture, near misses and incidents.

Learning never controls these outcomes on its own. The responsible claim is that development contributes to or influences them. Designing with the outcome in view makes that contribution easier to examine and keeps the work honest.

Confidence should sit alongside mastery. Capability without confidence may stay in the classroom. Confidence without evidence creates risk. Readiness means a person can perform and has a well-calibrated view of what they can do.

Build once, recompose for the work

Global development has to hold two truths at once: central coherence matters, and local meaning matters. A program that works in Amsterdam may not land in Shanghai or São Paulo.

The answer is not to recreate everything for every audience. Build a stable architecture of granular objectives and reusable resources, then recompose the journey around business priority, audience, culture, available time, risk and delivery model. Practice, examples and facilitation can become local without losing the common capability standard.

Technology can help organize objectives, personalize routes and surface evidence. It belongs in the background. Taxonomies classify work; inference is probabilistic; evidence is what a person actually demonstrates in a probe, simulation, observation or real assignment. Promotion and succession decisions should never disappear into a black box.

Six questions to start the capability turn

1. What business outcome is this development meant to support?
2. In which real situations must people perform differently?
3. What do head, hands, heart and heels look like in those situations?
4. Which existing strengths can learners build on?
5. Where will practice, feedback and reflection happen before, during and after formal learning?
6. What evidence will show that someone is ready, and when will we review the business outcome?

Training remains valuable. So do good content and skilled facilitation. But they are inputs, not the final outcome. Skills can be taught. Capability has to be built: through the learner, the experience, the people around them and the moments in which the work becomes real.