Imagine a team finishes a well-run workshop on handling customer objections. People enjoy it. Feedback scores are high. Everyone completes the course. Three months later, the same objections still stall the same deals, and reps still discount too early.
Nothing was wrong with the workshop. It was simply not enough on its own. Training is a good start. It is rarely the whole job.
What training does well
Training gives many people the same information at the same time. It creates a shared language, introduces a useful model, and explains why a skill matters. That is real value, and it is the first stage of building a skill. We described it as the "acquire" stage in the skill lifecycle.
The trouble starts when the first stage is treated as the finish line. People leave knowing more. Whether they behave differently is a separate question.
Why behavior stays the same
When a course does not change what people do, the cause is usually one of three things.
- No realistic practice. People hear about a conversation but never have one in a safe setting. The first real attempt happens with a real customer, and it is uncomfortable.
- No feedback. Without hearing what worked and what to change, people repeat their habits. Familiar habits are comfortable, especially under pressure.
- No second attempt. A single exposure fades. Most people lose much of what they hear if they do not use it soon afterward.
None of these is a content problem. Adding more slides does not fix any of them.
Knowing is not the same as doing
A person can explain a framework perfectly and still freeze in a live conversation. We covered this in knowing vs. doing. Recall happens in a calm room. Work happens with a person waiting for an answer and a clock running.
That is why completion rates and quiz scores say little about behavior. They show that information was delivered. They do not show that anyone can use it.
What actually changes behavior
The pattern is simple and repeatable. A person tries the skill in a situation close to real work. They get specific feedback. They try again. Over a few rounds, the new approach starts to feel natural. This is the loop behind what skill building actually means.
Notice what is different from a course. The person does most of the work, not the presenter. The attempts are spread over time instead of packed into one day. And every attempt produces something you can observe.
The work environment matters too
Even good practice can fade if the workplace pulls in another direction. A manager who never asks about the new approach sends a clear signal. So does a target that rewards the old behavior. A tool that makes the new step awkward has the same effect.
Managers have an outsized role here. A short conversation after a real call, a question about what someone tried, or a moment of specific praise keeps the skill alive between formal sessions. This does not need to be heavy. It needs to be regular.
How to tell whether training worked
Ask a different question. Instead of "did people finish the course?", ask "can people do the thing, and do they do it more often?"
To answer that, you need a clear description of the behavior. If you have not written one yet, skill mapping 101 shows how to describe a skill as something you can observe. Then look at how people perform in a realistic situation before the training, shortly after, and again some weeks later. The change across those points is your evidence. Where there is no change, the training is not the problem to solve. The missing practice is.
Where to start
Pick one recent training program that was meant to change behavior. Write down the one or two behaviors you hoped to see. Then add three things around it:
- A short realistic practice situation that people can repeat.
- Specific feedback after each attempt.
- A manager prompt that asks, a week later, what the person tried.
Compare how people perform before and after. You will learn more from that than from any satisfaction score.
myQuest Skills lets people practice realistic work situations with AI simulations and get feedback, and it shows managers progress and gaps across the team.
Next in this series: a first look: how skill data connects to business results
