The whistle cartoon
The centrepiece of the morning was a three-panel cartoon. A boy says: "I taught Stripe how to whistle." His friend replies: "I don't hear him whistling." The boy answers: "I said I taught him. I didn't say he learned it." That is the whole problem of corporate training in three speech bubbles. Delivery is not acquisition. A trainer can present flawlessly, tick every item on the agenda, collect glowing feedback forms — and still change nothing, because teaching happened but learning did not. My margin note from this slide: briefing and debriefing are different things, and listening is one way to measure. If I want to know whether learning happened, I have to stop performing and start listening for the whistle.
Learning, properly defined
The workbook defines learning as the acquisition of knowledge, skills and attitudes — KSA — that brings about a relatively permanent change in the behaviour of the learner. Every word is load-bearing. Acquisition: the learner has to take something in, not just sit through it. Knowledge, skills AND attitudes: knowing the standard, being able to perform it, and wanting to. And relatively permanent change in behaviour: if nothing is different a month later, no learning occurred. My note next to the definition: learning = process. The trainer's job is to design that process, not to deliver content.
Training, properly defined
Training is then defined as an activity whose purpose is to create a change in learners so that they consistently demonstrate the required behaviours, increasingly more accurately and automatically. The three adverbs are the quality bar: consistently (not just when observed), accurately (to standard), automatically (without needing to think hard about it). So learning is the outcome; training is one activity that can produce it. She also contrasted the behaviourist view (design activities that shape behaviour, level by level — my note says Lv1 → Lv2 → Lv3) with the cognitivist view (structure understanding, not just repetition). Good training borrows from both.
Case Study
the check-in briefing that taught nobody to whistle
I run short-term rental suites, so I tested the definition against something we actually do: front-desk onboarding for a new check-in flow. What we did: a one-hour briefing. Slides on the new steps, the deposit policy, the OTA edge cases. Everyone nodded. Attendance sheet signed — training "done". Run it through today's definitions and it falls apart. Knowledge: partially transferred, maybe. Skills: never practised — nobody actually processed a test guest through the new flow. Attitude: never addressed — the team privately thought the new flow was slower, so they quietly kept the old one. Behaviour change: zero within two weeks, which we only discovered when a guest complained about an inconsistent deposit charge. We taught. Nobody whistled. The fix, redesigned with today's lens: a 15-minute walkthrough, then every staff member runs two mock check-ins (skill), a discussion on why the deposit rule protects their own shift-end reconciliation (attitude), and a follow-up where a supervisor listens to real check-ins the next week (measurement by listening). Same content, completely different design — because the target is behaviour, not attendance.
Reflections
Two things to carry forward. The outcome of training is behaviour, and behaviour is observable — so every programme I design should name the behaviour it intends to change and how we will see it. And attitude is a first-class citizen in KSA; most failed training I have seen failed there, not on knowledge.