From knowledge to behaviour: why knowing is not the same as doing

An employee can know exactly what to do, and still not do it. That seems contradictory, but knowledge and behaviour are two different things. That distinction matters when organisations want to know whether a training actually had an effect.

Knowing is not the same as doing

Say someone has attended a safe-working training. Asked whether they should use protective equipment X in a given situation, they answer correctly. But a month later, they don't do it. Did the training fail? Not necessarily: the employee may still have the knowledge, but other factors influence behaviour.

From knowledge to application

You can view a learning process as a series of steps: knowledge, recall, understanding, application, behaviour, and ultimately result. Each step has different requirements. An employee can know the rule, be able to explain the rule, and correctly solve a scenario, and still behave differently in practice. That is why a knowledge test is not a complete measure of behaviour.

Why doesn't behaviour change automatically?

Behaviour is influenced by many factors: work environment, time pressure, social norms, role modelling, available resources, procedures, rewards, feedback, motivation, and habit. A training can influence knowledge and skills, but it does not have full control over all these factors. So be careful with claims like 'behaviour changes after this training'. A more realistic claim is that a training is designed to support knowledge and application.

The role of retrieval and scenarios

Retrieval practice can bridge learning and application: an employee gets not just 'what is the rule?', but 'what do you do in this situation?' That connects knowledge to a context. Scenarios are interesting for the same reason: they force the employee to make a decision, for example when asked what they do when they see a colleague skip procedure X. The employee then has to recognise the situation, retrieve relevant knowledge, and make a decision, which is closer to application than reproducing a definition.

But scenarios are still not real practice

This is an important nuance: a digital question can prepare behaviour or test knowledge, but it is not the same as behaviour in the real work environment. That's why, for some topics, you also need to look at observation, practical exercises, feedback, coaching, and performance data. A first responder, for example, should not just know what to do: certain skills also need to actually be practised, as also described in keeping safety and first-response knowledge sharp.

The training-retention-practice cycle

A strong learning journey can consist of training for new knowledge and skills, retrieval to bring knowledge back to mind, a scenario to practise applying it in context, feedback to correct and deepen it, practice to apply it at work, measurement to see what actually happens, and repetition where needed. That is a far richer model than just training followed by an evaluation.

What this means for training providers

This creates an interesting shift. A training provider can help its client not just with knowledge transfer, but also with knowledge retention and, in turn, application. The value proposition then becomes: we don't just deliver the training, we help make sure what was learned stays active over a longer period. That is a far stronger relationship with the client.

An example: safety and first response

Say: day 1 is the first-response training, week 1 brings a knowledge question, week 2 a scenario, week 4 a knowledge check, week 6 a practical question, week 8 a scenario, week 12 a retention measurement, and every year the practical training or refresher. The digital retention programme does not replace the practical training, it supports maintaining knowledge between the formal training moments.

How do you measure real impact?

You can measure different layers: knowledge (can employees reproduce the information?), retention (do they still know it later?), application (can they use it in a scenario?), behaviour (do they actually do it?), and result (does anything change in the organisation?). That last step is usually the hardest to attribute to a single training, which is why you should avoid causal claims when you only have training data, see also how to measure the return of a training.

The main takeaway

A training's only goal is not for employees to pass a test. The ultimate goal is often that employees act differently when it matters. But between knowledge and behaviour lie several steps, which is why knowledge retention matters, even though knowledge retention is not the same as behaviour change. A strong learning strategy accounts for both: learn, remember, apply, act, and measure. That is the shift from training to a genuine learning outcome.