The test training must eventually pass
A training session can be engaging, professionally delivered and highly rated—yet still make little difference to the work. Participants may enjoy the facilitator, remember the models and complete the evaluation form. Then Monday arrives.
The manager postpones the difficult conversation. The team uses the old process. The leader returns to the same decision habit. The programme created a positive event, but not practical capability.
The Monday Morning Test asks what changed when the participant returned to real work.
This is not an argument against knowledge or participant satisfaction. Both matter. It is an argument that they are incomplete measures. Learning earns organisational value when it becomes available for use.
Four levels of evidence
1. Exposure
The participant encountered an idea, model or method. They may recognise the terminology when they see it again. Exposure is useful, but it does not prove understanding.
2. Understanding
The participant can explain the idea accurately and distinguish it from related concepts. This is stronger than recognition, but explanation does not prove performance.
3. Competence
The participant can use the idea in a relevant case, simulation, role play or structured exercise. The conditions are still supported, but capability is becoming visible.
4. Application
The participant uses the capability in a real decision, conversation or task at work. The organisational environment now matters: time, systems, incentives, manager support and competing priorities can either enable or block transfer.
Why transfer breaks down
When learning does not transfer, the course is not always the only cause. Several barriers can sit between the training room and the workplace:
- The programme was not connected to a genuine performance need.
- Participants understood the concept but did not practise it.
- The examples were too generic to resemble the job.
- Managers did not reinforce or model the expected behaviour.
- Systems, workload or incentives rewarded the old behaviour.
- No one asked for evidence of application afterwards.
This matters because “the training did not work” can conceal a design problem, a transfer problem, an environmental problem or a combination of all three.
Design backwards from Monday morning
A stronger programme begins with the work, not the slide deck. Before content is finalised, ask:
- What should participants do differently?
Express the outcome as behaviour, a decision or a practical task. - What makes that difficult now?
Identify gaps in knowledge, skill, judgement, confidence or environment. - What must they practise safely?
Create realistic cases, conversations and decision exercises. - Where will they apply it?
Link the training to a real workplace situation soon after the session. - What evidence will be inspected?
Decide what the participant, manager or programme owner will review.
Examples of credible evidence
The correct evidence depends on the programme. A leadership course should not be measured in exactly the same way as systems training. Useful evidence may include:
- A clearer board recommendation with evidence, risk and next steps.
- A completed performance conversation followed by documented actions.
- A stakeholder plan used in a live negotiation or change initiative.
- A manager's observation of improved delegation or feedback.
- A decision record showing how assumptions and trade-offs were handled.
- A 30- or 60-day review of the behaviour the programme targeted.
A practical question for buyers
Before approving a programme, do not ask only, “What topics will be covered?” Ask:
What will participants practise, where will they apply it, and what evidence will tell us that the learning travelled?
That question changes the relationship between provider, participant, manager and organisation. It turns training from an isolated event into one part of a capability system.