Why capability, not training, drives performance

There is a familiar moment in the annual organisational review of learning and development. Impressive figures are presented. Hundreds of employees have attended programmes. Completion rates are healthy. Participant feedback is positive. The organisation has invested heavily in leadership, digital skills, customer service, project management or some other priority area. The learning calendar has been busy, and the budget has been used.

Then someone asks a rather different question. What can the organisation now do better?

Not what did people enjoy. Not what new concepts were introduced. Not how many learning hours were delivered. But what can the organisation now do, consistently and at a higher standard, that it could not do before?

It is a reasonable question. Yet it is one that many learning reports struggle to answer.

This is not because learning teams do not care about performance. Nor is it because the courses were necessarily poor. The deeper problem is that organisations have become accustomed to treating participation in learning as evidence of increased capability. They are not the same.

The appeal of visible activity

Courses are attractive partly because they are tangible. A need can be identified, a provider selected and a programme commissioned. People attend. Evaluations are completed. Certificates may be issued. Progress can be reported to senior leaders. Something visible has happened. We can easily tick the activity box and quote KPIs.

Capability is much less tidy. It develops unevenly. It depends on context, opportunity and reinforcement. It can be difficult to distinguish from experience, confidence, sound management or improved organisational conditions. It rarely arrives on a single date and is seldom attributable to one intervention.

This creates a natural bias towards what is easiest to count.

Organisations report how many people attended, how many modules they completed and how positively they rated the experience. These measures are useful. They can tell us whether people engaged and whether the programme was competently delivered.

They cannot, by themselves, tell us whether managers are leading more effectively, decisions are being made more intelligently, or strategy is being executed with greater discipline.

Attendance is evidence of activity. It is not evidence of capability.

Learning matters, but it is not enough

None of this, of course, is an argument against formal learning.

A well-designed course can introduce new knowledge, interrupt familiar thinking and expose people to practices they have not previously encountered. It can give participants a shared language. It can create time for reflection that ordinary working life seldom provides. Sometimes a course is precisely the right intervention.

The mistake is to expect the course to do work that belongs to the wider organisation.

A participant may leave a programme understanding what effective delegation looks like. That does not mean they will delegate effectively when the pressure returns and their team lacks experience and their own manager continues to reward personal control.

A leader may learn how to conduct a more rigorous strategic discussion. That does not mean the quality of strategic decision-making will improve if information still arrives late, disagreement remains unwelcome and important decisions are made outside the formal forum.

Someone may understand the principles of innovation perfectly well. That understanding will count for little if modest experiments require multiple approvals and a sensible failure remains more damaging to a career than cautious inaction.

Knowledge may be present while capability remains absent.

The distinction matters because capability is not simply what somebody knows. It is what they are reliably able to do, in the circumstances in which performance is actually required.

The return to work

Consider what happens after a genuinely good development programme.

A participant returns with fresh energy, a notebook full of ideas and perhaps two or three commitments about what they intend to do differently.

Within hours, the inbox fills. The calendar closes around them. The issues waiting before the programme remain unresolved. Their manager wants progress on yesterday’s priorities, not an extended conversation about last week’s learning. Colleagues continue to work in familiar ways. Existing systems and routines reassert themselves.

Very little – if anything – in the workplace has changed simply because the participant has changed.

This is not a failure of character. It is a reminder that people do not return from learning to a neutral environment. They return to an organisation with established habits, incentives, expectations and pressures. Those forces are powerful. They may be more powerful than anything said in the training room.

The workplace is, therefore, not simply the place in which learning is later applied. It is part of the mechanism through which capability is either strengthened or defeated.

When the diagnosis is incomplete

I have seen organisations respond to weak execution by sending people on project management programmes. Sometimes that helps. At other times, the underlying problem is that priorities change too frequently, sponsors do not make timely decisions, and nobody is clear who has the authority to resolve a blockage. The presenting problem sounds like a skills gap. The deeper issue is operating discipline.

Another organisation may respond to inconsistent management by investing heavily in leadership development. Yet its managers carry excessive workloads, receive little useful feedback and observe senior leaders behaving in ways that contradict the programme. The development may be excellent. The environment still teaches the stronger lesson.

Innovation provides another example. An organisation may train people in creativity, experimentation or design thinking while retaining a governance system that treats uncertainty as incompetence. Employees soon learn that talking about innovation is encouraged, while taking the risks associated with it is not.

In each case, training is asked to compensate for a problem it did not create and cannot resolve alone. The programme may not be the problem. The diagnosis may simply be incomplete.

Begin with capability

A more useful conversation begins elsewhere.

Instead of starting with the learning catalogue, begin with what the organisation needs to become able to do.

Perhaps it needs to make better decisions at greater speed. Perhaps managers need to develop others more consistently. Perhaps the institution needs to execute across functional boundaries, use data intelligently or adapt more quickly to changes in its environment.

That leads to a different set of questions:

• What are we trying to become better able to do?
• Why are we not able to do it consistently today?
• Is the gap primarily one of knowledge, experience, judgement, authority or organisational design?
• Where will people have the opportunity to practise?
• What must managers do differently?
• What systems or incentives may reinforce the old behaviour?
• What evidence would convince us that capability has genuinely grown?

Formal learning may still be part of the answer. Often it should be. But it becomes one element within a broader, more coherent response.

The organisation may also need to redesign work, clarify decision rights, create stretch assignments, strengthen management practice, provide coaching, improve access to information or change the way performance is reviewed.

Capability is rarely produced by a single instrument.

Learning through real work

This is why the strongest development experiences are often connected to work that matters. A programme on strategy becomes more powerful when participants apply it to a real strategic choice. Leadership development becomes more consequential when managers practise difficult conversations and reflect on what happens. Systems thinking becomes useful when it is applied to a blockage the organisation genuinely needs to resolve.

The point is not to turn every programme into another work meeting. People still need intellectual space, outside perspectives and the opportunity to examine assumptions. But the boundary between learning and work should be more permeable than it often is.

People build capability through a combination of understanding, application, practice, reflection, feedback and repeated experience. If most of those elements are absent, it should not surprise us when a good course produces limited change.

Capability is a leadership responsibility

Learning teams have an important role in all of this. They can improve diagnosis, design stronger experiences, create opportunities for practice and help the organisation gather better evidence. But they cannot do everything.

They cannot, on their own, give managers time to develop others. They cannot change decision rights, alter incentives or prevent strategic priorities from shifting. They cannot ensure that senior leaders model the behaviours being taught. They cannot create psychological permission for experimentation if the wider culture punishes mistakes. Those are leadership choices.

If capability is essential to strategy, its development cannot be regarded simply as an HR activity. It requires the attention of executives, functional leaders and line managers. It deserves the same seriousness given to technology, capital and operational infrastructure.

Courses can support that work. They cannot substitute for it.

The answer, then, is not literally to stop sending people on courses. It is to stop sending them without examining the organisation to which they will return.

Before approving the next programme, perhaps the leadership team should ask not only what people will learn, but what will be different in their work when they come back.