They Know It Cold. They Just Don't Do It: Why More Training Never Fixes Week Four

Two weeks ago I asked you to look at week four. Last week I took apart the vendor-swap reflex. This week is the second reflex, and it's the one that feels most responsible: more training.

Run the test first

Take the three people on your team who've gone furthest back to the old way. Check their training records.

In 29 years of walking sales floors I've found the same thing every time. They attended everything. They passed the quiz. Often they scored highest. The people who slide in week four aren't the ones who missed the training. They're the ones who aced it.

That one fact should change what you buy next, because the refresher you're about to schedule is going to teach them something they already know. They'll nod. Friday will keep moving.

I'm not against training. I've delivered a great deal of it. I'm against asking it to do a job it was never built for.

Training answers the wrong question

Training answers one question: do they know how? By week four, they do. Every one of them could pass the exam in their sleep.

Week four asks a different question: do they do it on a bad Tuesday, with a quota due, when nobody's watching? That isn't knowledge. It's a default. And you can't train a default. You install it, or the old one stays exactly where it was.

So every refresher lands the same way. Attendance high, quiz scores high, the six o'clock notebook untouched. The method isn't wrong because your enablement team is bad. It's wrong because it's aimed at a week that already passed.

The numbers

Writer's 2026 enterprise survey found 79 percent of executives reporting adoption challenges, up double digits in a year. That year had more AI training in it than any year in history. Fortune reported a survey of 2,400 knowledge workers in which 29 percent admit they avoid the tools, ignore the new process, or pretend to use a system they never touched. Trained workers. Certified. Pretending.

More training, worse adoption, for a year running. When the fix scales up and the problem doesn't scale down, the fix is pointed at the wrong thing.

The refresher that changed nothing

A head of enablement told me about hers. The slide showed up in month two, so she did what the playbook says. She rebuilt the deck: shorter, sharper, a live demo, a certification at the end. Attendance was 96 percent. The pass rate was 100.

Two weeks later she walked the floor. Same notebooks, same six o'clock catch-up. Her best rep had the certificate pinned above the notebook.

"They know it cold," she said. "They just don't do it."

That sentence is the whole problem in seven words. She stopped building decks that month and started asking what happens on Tuesday.

Where the budget should go

Imagine the training budget spent on the week that decides. Not three days before launch, when everyone's fresh and nothing's been tested, but weeks three and four, when the quarter's biting and the old way is whispering.

Same dollars, different week. The manager gets a script for the one conversation that matters. The team gets one behavior to hold instead of forty features to remember. And in March the platform's still running because the default moved, not because the deck was good.

Not the launch. Not the tool. Not the training. Next week is the last place everyone looks, and the one that hurts: the people. I'll show you why your best ones go back first, and why that's the most hopeful fact in this whole series.

If you want the number for your own team, the Caveman Code Diagnostic takes two minutes.