Learning and development (L&D)

Every organisation develops its people whether or not it has a department for it. Someone shows a new hire how the system really works. A project goes wrong and everybody adjusts. L&D is the attempt to make that happen deliberately, in the direction the business is heading.

Why the simple definition misleads

The usual definition, "the function responsible for training employees", makes L&D a supplier of courses, judged on how many it ran and how much people enjoyed them. Under that definition a busy L&D team and an effective one look identical.

The word doing the real work is development. Training closes a known gap in a known skill: someone cannot use the new system, so you teach them the system. Development builds capability for work that does not exist yet, such as the engineer who will be running a team in two years. One is a task. The other is a bet.

If your L&D function can tell you how many training days it ran but not which business problem got smaller, it is a booking service with a nicer name.

It also gets confused with its neighbours. HR owns the employment relationship: hiring, pay, policy, exits. L&D sits inside it but answers a different question, capability rather than compliance. Talent management decides who moves where. Enablement is L&D scoped to one revenue number.

What it looks like in practice

In a real week an L&D function does several things at once. Someone is working out whether a business problem is genuinely a skills problem, which it often is not. Someone is designing a programme, someone is booking facilitation, and someone is fighting the learning platform.

A worked example. A support team's escalation rate climbs and the request reaching L&D is "we need communication training". The first move is to listen to the calls. If agents escalate because a policy is ambiguous and being wrong is punished, no course fixes that. If they handle facts well and emotion badly, that is a real skills gap needing practice under pressure. Telling those apart is the job.

Training vs learning and development

Neither column is the villain. Good training is difficult and most organisations under-invest in it. The failure mode is running the left-hand column and reporting it as the right-hand one.

How to build an L&D function that works

• Diagnose before you design. Ask what someone would be doing differently if the problem were solved. If nobody can answer in observable terms, you do not have a brief. Many requests dissolve here, which is the point.
• Design for practice, not coverage. Adults change behaviour by doing the thing badly somewhere safe, getting feedback, and doing it again. David Kolb's cycle of experience, reflection, conceptualising and testing underpins experiential learning.
• Put the manager in the loop. Transfer depends on whether the person's manager expects it. Five minutes of "here is what I want you to bring back", then a check-in at the next one-to-one, beats an extra module.
• Space it out. Hermann Ebbinghaus showed in the 1880s that memory for new material decays sharply without retrieval. Revisiting and testing beat one long day, which is awkward for the annual offsite.
• Teach managers to coach. Most development happens in ordinary work conversations. The GROW model and timely, specific feedback move capability further across a year than any programme.

People will not practise unfamiliar behaviour where mistakes are expensive, so psychological safety is infrastructure, not a wellbeing extra. And behavioural capability, which covers most soft skills, cannot be read about. It needs live practice, which is why formats like outbound training earn their cost.

How to tell whether it is working

Donald Kirkpatrick's four levels, reaction, learning, behaviour and results, are a sensible hierarchy. Most organisations measure level one, then report level four as though it followed.

1. Treat reaction scores as logistics data. People rate an engaging session highly whether or not it changed anything, and an uncomfortable one lower.
2. Ask at ninety days, not at the door. What is this person doing now that they were not doing before, and what got in the way?
3. Watch behaviour where it happens. Sit in the meeting. Listen to the call. Self-reported confidence rises after almost any programme and predicts little.
4. Name the business number in the brief, before the work starts. A metric chosen afterwards is chosen to flatter.
5. Use success cases. Robert Brinkerhoff's Success Case Method: interview the people it clearly worked for and those it did not. The difference is usually in the conditions, not the content.

Be straight about the limits. Attribution is hard: the quarter the leadership programme ran is also the quarter the reorganisation landed. Anyone quoting a precise return-on-investment figure for a communication programme is modelling, not measuring. The defensible claim is narrower: this behaviour is now observable in this team, and here is what happened downstream.

Myths and common mistakes

• Learning styles. The belief that people are visual, auditory or kinaesthetic learners and should be taught accordingly is among the most popular ideas in the field and the least supported. Studies designed to test it properly have not found the predicted benefit. People have preferences; teaching to them does not improve results.
• The learning pyramid. The chart claiming we remember ten per cent of what we read and ninety per cent of what we teach has no traceable source. It is often pinned on Edgar Dale, whose Cone of Experience carried no percentages. Active practice does beat passive exposure; the numbers are fiction.
• A big catalogue is a strategy. A library with low completion is a cost, not an asset. A curriculum says what someone at this level should be able to do, and in what order. A catalogue is a shop.
• L&D owns development. It owns the system. Managers own their people's development, and a function that lets them outsource it delivers courses nobody reinforces.

The through-line is simple. L&D is not the business of delivering training. It is the business of deciding what an organisation needs to be able to do, judging honestly whether learning is the right lever, and making the change survive the week after everyone goes back to work.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.