Why. How. Why again. Skip any layer and the learning never sticks.
Most training programs give you education or training — rarely both, and almost never in the right order.
The sequence that actually works is what I call the Why Sandwich: start with why it matters to them, deliver the practical how, then close with why it matters even more to them now that they can do it.
The first why creates motivation. The how builds capability. The second why converts capability into action.
Skip any layer and the learning either never starts or never sticks.
Before you build a single learning objective — make sure you're solving the right problem.
I was called in once to train a customer service team because productivity was dropping. Before I developed a single piece of training, I did what I always do first — an assessment. What I found had nothing to do with skills. The department was being buried by incoming emails, and a strict response-time policy forced representatives to constantly switch between calls and their inboxes. They weren't underperforming. They were drowning in a system that made it impossible to perform.
That wasn't a training problem. That was a process problem wearing a training costume.
Training gets called in to fix a lot of things that aren't training problems. Unclear expectations. Broken processes. Poor tools. Conflicting priorities. Management decisions that haven't been communicated.
Before you build a single learning objective, ask the honest question: is this actually a training problem?
If the answer is no — fix the real problem first. Training on top of a broken process doesn't fix the process. It just gives people better skills for navigating a system that's still working against them.
Here's something most organizations believe about themselves that isn't true: they think they have a safe learning environment. They don't.
They have a polite environment. A professional environment. An environment where people have learned — often through painful experience — exactly what they can and cannot say, ask, or admit without consequences. That's not safety. That's an illusion. And you can't learn inside an illusion.
Most of us carry the evidence of this from our own school days. The embarrassment of getting an answer wrong in front of the class. The decision to stop raising your hand rather than risk looking stupid.
Your job is to put the red pencil away.
Building that environment isn't a speech. It isn't a poster on the wall about psychological safety. It's a series of moments — each one sending an unconscious message about what's actually true in this room right now.
The environment isn't set before the session starts. It's set in the first five minutes. Sometimes the first five seconds.
Get it right and everything works. Get it wrong, and it's cleanup in aisle 5.
Watch young children play soccer, and you'll see twenty kids chasing the same ball, crowding the field, leaving everything else open. Watch professionals play, and you'll see something completely different — eleven people covering the entire field, each owning their position, each creating the space that allows everyone else to take advantage of opportunities.
Cross-functional training is how organizations make that transition. From chasing the ball to owning the field.
When people from different parts of the organization train together, they don't just learn the skill — they learn how their work connects across functions. That understanding breaks down the silos that slow everything down and creates the kind of organizational awareness that no org chart ever delivers.
The graveyard of good training is full of skills that never made it back to the job.
Don't teach a skill and then let it sit unused. End every session with a concrete action plan — specific, immediate, and tied directly to real work that's already waiting. Not think about how you might apply this. Today. This week. The next time this situation shows up — which is probably tomorrow.
Unused skills evaporate. Applied skills compound.
The talent drought is coming. Part 4 →