There’s a moment, in nearly every L&D program I’ve audited, where you can see the seams. A module that took six weeks to build gets completed in eleven minutes — mouse-clicks audible through a webcam — and the learner walks back onto the floor knowing exactly what they knew before. The dashboard, of course, shows a green checkmark.
This is the corporate L&D bargain as most organizations have come to understand it: training is a thing you make. You write a curriculum, you build the slides, you wrap it in SCORM, you push it to the LMS, you measure completion. The output is content. The metric is consumption.
And it doesn’t work. We all know it doesn’t work. The question is why we keep doing it anyway.
The content trap
I think the answer is that “training is content” is structurally convenient. Content can be budgeted. Content can be scoped. Content can be outsourced, version-controlled, and reported on. Content fits inside a project plan with a beginning, a middle, and a launch date. Everything our org chart wants training to be, content already is.
The trouble is that the human on the other end of the content isn’t consuming — they’re negotiating. Every learner in every module is silently asking three questions, and the answers determine whether the training lands or evaporates:
- What is this asking of me? — effort, attention, time, the cost of looking stupid.
- What do I get back? — capability, confidence, fewer escalations, a faster shift.
- Who’s holding up their end? — will my manager actually let me practice this? will the system support what I’ve learned?
When all three answers line up, training takes. When even one of them is missing or ambiguous, the click-through rate goes up and the recall rate goes down. The dashboard still turns green. Everyone agrees the program was a success. Nobody changed how they work.
A module is a deliverable. A contract is a relationship. The first you ship and forget. The second you have to honor.
What a contract looks like
Reframe the same project as a contract and the whole architecture shifts. You’re no longer the studio shipping training to an audience. You’re a negotiator brokering an agreement between three parties — the learner, the operator (their manager, the floor lead, the service supervisor), and the business sponsoring the program.
Each party has obligations:
The learner agrees to
Show up with intent. Engage with the material. Try the thing in a low-stakes context before doing it for real. Notice when their behavior is changing — not because the training told them to, but because the work is asking different things of them.
The operator agrees to
Give people the space to practice. Catch the small failures that come with new skill before they become big ones. Reinforce what was taught in the moments it shows up on the floor. Most critically: not punish the learner for the cost of getting better.
The business agrees to
Make the system the training describes the system that actually exists. If the module says “always check the panel first” and the panel takes ninety seconds to boot, the business has broken the contract before the learner ever touched the module. Training cannot patch a broken process. It can only describe the process honestly — and a good L&D leader holds the business accountable to that honesty.
Pull up the last three training programs you launched. For each one, write down what the learner, the operator, and the business each agreed to. If you can’t articulate all three — in one sentence each, no hedging — you didn’t ship training. You shipped a module.
Why the framing matters
Designing training as content makes you optimize for the wrong things. You make modules shorter, because completion rates go up when they’re shorter. You add scenarios, because engagement scores go up when there are scenarios. You make the post-test easier, because pass rates go up when the test is easier. Every optimization moves the metric and erodes the outcome.
Designing training as a contract makes you optimize for the right things. You ask: what is the smallest commitment from each party that still produces the change? You ask: where is this contract going to be tested first — and is the learner ready for that test? You ask: what happens the day after the training ends, and have we built that day in?
The work itself doesn’t look that different from the outside. You’re still building modules. There’s still a launch date. The deliverables look familiar. But the conversations you have before the build — with the sponsor, with the floor, with the people who’ll actually live with the outcome — are radically different. You’re not negotiating scope. You’re negotiating obligation.
The hard part
The hard part is that contracts can be broken. Modules, by virtue of being content, are unbreakable — they exist whether anyone uses them or not. A contract requires all three parties to keep showing up. The learner can lose interest. The operator can revert to old habits under pressure. The business can change strategy and orphan a curriculum that took six months to build.
But this is the point. Training that’s designed to be honest about its dependencies is also designed to survive them. You build with the breakage in mind. You measure the contract, not just the module — not just completion, but reinforcement, application, and the operator’s side of the deal.
And when the contract holds — when the learner takes it seriously, the operator backs them up, and the business honors the system it described — you don’t get a checkmark on a dashboard. You get the thing the dashboard was always trying to approximate.
You get someone who knows how to do their job.
— Jonathan