From knowledge to capability: bridging the gap

A representative who can recite the data and cannot hold the conversation has knowledge, not capability.

Why the gap exists

Knowledge transfers easily. It can be presented, read, tested and certified, and the organization can demonstrate afterwards that it was delivered. Capability transfers badly, because it forms only through attempts, failures and corrections in a real setting with real consequences.

Learning functions are usually measured on delivery: courses run, people trained, completion rates achieved. That measurement bias quietly pushes programme design toward what is easy to demonstrate rather than what is hard to build. Nobody decides to prioritize knowledge over capability; the reporting system decides it on everyone behalf.

The gap is most visible at the point of application. Ask a group what good customer engagement looks like and most will answer well. Watch the same group in the field and the variance is enormous. That distance between articulate and able is the whole problem.

The three-stage progression

In our work the progression that holds is consistent: understand, apply, sustain.

• Understand: the input stage. Efficient, measurable, and the only stage most programmes fund properly.
• Apply, supervised practice in a real situation, with feedback close enough in time to be useful. Expensive, awkward to schedule, and where learning actually begins.
• Sustain, the point at which the behaviour persists without support. Reached only through repetition over months, and almost never inside the life of a programme.

Programmes that stop after the first stage are not a partial success. They frequently produce no durable change at all, while consuming the budget the later stages required. This is worth stating plainly, because a half-funded capability programme is often worse value than no programme, having spent real money to produce a temporary feeling of progress.

The line manager is the mechanism

Nothing determines whether learning becomes capability more than the immediate manager. A manager who asks about it, observes it and coaches it converts a workshop into a habit. A manager who does not, cancels it: usually without intending to, simply by never referring to it again.

Representatives read this accurately. If the manager never mentions the content after the workshop, the reasonable conclusion is that it was not important, and behaviour reverts within weeks.

This has an uncomfortable implication for programme design: developing the manager is not an adjunct to the programme, it is a precondition for it. Rolling out capability content to a field force whose managers cannot coach is a well-intentioned way to waste a budget.

Practical design choices

Several choices consistently improve transfer, and most of them cost little.

• Shorten the input and lengthen the application period. Two hours plus six weeks beats two days plus nothing.
• Build the field task into the programme as a requirement rather than a suggestion.
• Give managers a short, specific coaching guide tied to the content, not a general coaching model.
• Review application publicly, so that doing it is visibly expected and not doing it is visibly noticed.
• Space the content. Three short sessions across a quarter outperform one long session, reliably.

None of these are expensive. They are, however, considerably less comfortable than delivering a well-received workshop and moving on, because each one creates a point at which the organization can see whether the learning is actually being used.

What this looks like in practice

Consider a selling skills programme, which is the most common capability investment in commercial pharma and the one most often delivered as an event.

The event version runs for two days, covers a model, includes role-play, and finishes with an evaluation form. Satisfaction is high. Six weeks later, observation in the field shows perhaps one in five representatives using any part of it, and usually the part that most resembles what they were already doing.

The transfer version runs for half a day on the model, then requires each representative to apply one specific element in a defined number of real calls over the following month, with the manager observing at least twice and discussing only that element. A second half-day follows, built entirely around what actually happened. A third element is introduced only once the first is established.

The second version takes longer in calendar time and consumes more managerial attention. It costs less in classroom delivery. And it produces observable change in field behaviour, which the first version reliably does not.

The difference is not the content. Both versions teach the same model. The difference is that one is designed around the moment of application and the other around the moment of delivery.

Measuring capability rather than completion

If the goal is capability, completion rates are the wrong measure and will actively mislead.

Useful alternatives are observational: a manager rating of the behaviour against a defined standard before and after, the proportion of field visits in which the behaviour is observed, or a simple structured self-assessment paired with a manager view to surface gaps in perception.

These take more effort to collect than a completion report, and they occasionally produce unwelcome findings. That is precisely their value. A measure that cannot return bad news is not measuring anything.