Why most small-business training dies in week two (and the one fix that works)

Every owner I've worked with has told me some version of the same story. They built an onboarding program. It was thorough. People were enthusiastic for about four days. By the second week, the new hire was shadowing whoever happened to be free, the binder was in a drawer, and the owner was back to answering the same questions they'd written the program to eliminate.

The usual diagnosis is motivation — the new hire didn't care, the manager didn't enforce it, the culture wasn't there. In fifteen years of teaching a licensed trade to adults, I never once saw motivation be the real cause. It was always sequencing.

What week two actually looks like

Here is what happens. Week one is orientation: history, values, where the bathroom is, how to clock in. It's easy and it's low stakes, and everyone gets through it. Then week two opens with the first real skill — and that skill quietly assumes three things the learner was never taught. They don't know they're missing those things. They just feel stupid, and adults who feel stupid stop showing up to the thing that made them feel that way. Not dramatically. They just start finding reasons to be elsewhere when the training is supposed to happen.

Adults don't quit training because it's hard. They quit because step three assumed step two, and nobody told them step two existed.

In cosmetology school, the failure point was almost always the same: a student would be asked to execute a service that depended on a foundational technique they'd been "shown" once in a demonstration but had never actually practiced to competence. The curriculum said they'd covered it. They hadn't learned it. Everything built on top of it wobbled.

The one question

Before I write a single lesson now, I ask one question about the outcome: What must this person be able to do, unassisted, on the day after training ends? Not know. Do. Then I work backward. What does that action require? What does each of those requirements require? I keep going until I hit things the learner can already do on day one. That chain, reversed, is the curriculum.

It sounds obvious. Almost nobody does it. Most training is built forward from "what do we want to tell them" rather than backward from "what do they need to be able to do," and the gaps only show up when a real person hits them in week two.

The fix, concretely

Take your existing program and find the first module where someone has to perform rather than listen. Write down every skill that module silently assumes. Then check whether each of those skills has its own practice step earlier in the sequence — not a mention, not a demo, a step where the learner does it and someone confirms they can. Wherever the answer is no, you've found where your program dies. Add the step. Your week-two dropout problem will mostly disappear, and you'll have done it without touching a word of your content.

This is also the first thing I build into the Training Platform: outcome first, then a dependency chain, then a check at every link. It's not sophisticated. It just respects how adults actually learn.