Training is the most common investment firms make in vulnerability. It is also the one most likely to fade. Here is why, and what to do instead.
If we asked every firm we have worked with to name the first thing they did when vulnerability became a priority, the most common answer would be training. It is the natural starting point. Colleagues need to understand what vulnerability is, how to recognise it, and why it matters.
We are not against training. Good training raises awareness, builds empathy, and gives colleagues a shared language. But training alone does not create lasting change. And in many firms, it has become the default investment: the thing you do when you want to demonstrate action, even when the problem sits somewhere else entirely.
Why training fades
We regularly speak to colleagues who have completed vulnerability training and found it valuable. They describe the case studies, the discussions, the moments of realisation. And then they go back to their desks and deliver the same process they delivered before.
This is not a failure of the training. It is a failure of the environment the training sits within. If the processes, tools and support options have not changed, awareness has nowhere to go. A colleague who can recognise vulnerability but has no supported route to respond to it is in a worse position than before. They now see the problem clearly but cannot act on it.
Within six months, the impact of standalone training has typically faded. Not because colleagues have forgotten what they learned, but because the organisation has not given them anything to do with it. The awareness remains, but the motivation to act on it has been eroded by the reality that the system has not changed.
The difference between training and capability
Training is an event. Capability is a state. Training tells colleagues what vulnerability is. Capability means they know what to do when they encounter it, and the organisation supports them to do it.
Capability requires three things working together. First, colleagues need to understand vulnerability and its impact on the customer. Training does this. Second, they need processes and tools that respond when a vulnerability is identified. This is Inclusive Design. Third, they need to see that their actions lead to different outcomes. This is feedback and evidence.
When all three are in place, colleagues do not just recognise vulnerability. They respond to it confidently, consistently, and in ways that lead to tangible change for the customer. This is what improving vulnerable customer outcomes looks like at the colleague level.
What capability looks like in practice
In the firms where colleague capability is strongest, it has not come from a training programme. It has come from involvement. Colleagues who participated in co-discovery and co-design workshops, who heard directly from vulnerable customers, who helped shape the solutions carry that learning far longer than any training course could.
This is one of the most powerful effects of Inclusive Design. The methodology does not just produce better services. It produces more capable colleagues. People who have been part of the process understand why things have changed, not just what has changed. They become advocates, not just implementers.
It also extends beyond frontline teams. Operational embedding includes building capability in non-customer-facing roles: process designers, MI analysts, team leaders, and decision-makers who shape the environment colleagues work in. If vulnerability capability only exists at the front line, it will always depend on individual effort rather than systemic support.
Learning by doing
The most effective approach we have seen combines structured learning with practical involvement. Colleagues learn about vulnerability by improving their own services. They hear from vulnerable customers. They see the data. They contribute to the design. And they experience the difference when the new process goes live.
This is learning by doing. It sticks because it is real. It builds confidence because colleagues have seen the evidence. And it sustains itself because the capability is embedded in how the team works, not in a course that someone attended once.
If your current approach to vulnerability relies on periodic training, the question is not whether the training was good. The question is whether it changed anything. If your colleagues are more aware but not more equipped, the gap is not in their learning. It is in your operation.
Let’s talk
If you want to build colleague capability that lasts, we can help. Our Inclusive Design methodology builds understanding and confidence through involvement, not just instruction. A Vulnerability Review is a good starting point for understanding where your colleagues have the awareness but not the tools to act on it.