Why Most Training Programs Fail Before They Start
I used to run workshops where we'd spend three days trying to shift how people thought about their work. By day two, everyone was nodding along, saying the right things. By Monday back at the desk, every single person was right back to their old routines. I've spent the last decade figuring out why that gap exists and how to actually close it. The short version is that traditional education treats human potential like it's a container you fill. That's not how it works. It's not a course you sign up for. It's a way of structuring learning so that what someone figures out on their own sticks. The core mechanism is deliberate friction — creating situations where the learner has to struggle productively with a problem before you offer any scaffolding. Most trainers do the opposite. They hand you the framework, walk you through three examples, and then give you a worksheet that mirrors the exact pattern you just saw. That produces compliance, not capability. I'll walk you through how this actually plays out in practice, because the theory is simple but the execution is where everyone messes up.
The Method
Start by identifying the specific capability you want someone to develop. Not a general skill like "better communication" or "stronger leadership." Something concrete. A project manager who needs to deliver bad news to stakeholders without the conversation collapsing. A developer who needs to read someone else's codebase without immediately rewriting it. Name the exact behavior change. Once you have that, resist the urge to teach anything. Give the person the real scenario first. Let them fail through it. I remember working with a senior engineer — ten years in the role, technically solid, completely unable to push back on product management when requirements were unrealistic. Every time, he'd say yes, take on the work, and then miss the deadline by two weeks. He knew he had a problem. He just didn't know how to fix it. So I put him in a room with a role-play exercise where the product lead was asking for a feature that was clearly impossible in the given timeline. I didn't give him any scripts or phrases to use. I just watched. He said yes. Of course he did. Then we ran it again. Same result. Third time, same result. Only on the fourth iteration, after he'd genuinely felt the discomfort of saying yes and watching everything fall apart, did I intervene. I showed him three specific ways to push back that preserved the relationship while being clear about constraints. By that point, he actually wanted to learn them. Not because I told him to, but because the failure had created a real need for the solution.
That sequence — raw attempt, repeated failure, targeted intervention — is the entire engine. Everything else is decoration.
Get the Full Details
Why This Works (And Why It Feels Wrong)
The reason deliberate friction works is because of something called the desirable difficulty effect. When learners encounter a challenge that's hard enough to be frustrating but not so hard that they give up entirely, the brain encodes the subsequent learning much more deeply. You can see it in the data. Studies on retrieval practice, spacing, and interleaving all point to the same conclusion: learning that feels effortful in the moment produces better retention and transfer than learning that feels smooth. The problem is that both educators and learners hate it. Educators feel like they're not doing their job when they sit back and watch someone struggle. Learners feel like they're not getting value when there's no clear instruction to follow. This is why most programs default to the lecture-plus-worksheet model. It feels productive. Everyone is engaged. The room feels alive. The actual learning is shallow. There's a counter-intuitive piece here that people miss. The struggle phase needs to be time-boxed. If someone grinds on a problem for forty-five minutes and still isn't getting anywhere, you've crossed from productive friction into learned helplessness. I usually set a hard limit of twelve to fifteen minutes for the initial attempt, depending on the complexity of the task. After that window, if they haven't found a path forward, you step in with a hint — not the solution, a hint. Something that narrows the search space without giving away the answer. A question like "What would happen if you reversed your assumptions about what the stakeholder actually needs?" works better than any scripted response I could hand them.
The Common Pitfalls
The biggest mistake people make is choosing scenarios that are too abstract. You cannot build a real capability through hypothetical exercises. The scenario has to match the actual conditions where the person will need to use the skill. If you're teaching someone to negotiate scope with clients, the role-play needs to involve the kinds of clients they actually deal with, using the kinds of language those clients actually use. Generic stakeholder personas produce generic responses that don't transfer. Another pitfall is not varying the conditions between iterations. If you run the same exercise three times with the same partner and the same constraints, the person memorizes the pattern rather than building flexibility. I always change at least one variable between rounds — different personality type, different urgency level, different information asymmetry. The skill needs to work across variations, not just in the one scenario you practiced. There's also the feedback problem. After each iteration, the debrief needs to be specific and evidence-based. "You handled that well" is useless. "When you said 'let me think about it' instead of giving a direct answer, the stakeholder immediately escalated the perceived risk" is actionable. I use a simple framework: observe what actually happened, name the mechanism, suggest one adjustment for the next round. That's it. More than that overwhelms the learner and dilutes the signal.
Where This Breaks Down
Deliberate friction does not work for everything. If someone lacks foundational knowledge in a domain, throwing them into a hard scenario is just torture. You need to establish baseline competency before you introduce productive struggle. Teaching someone to write without first showing them how sentence structure works is not education, it's cruelty. It also doesn't scale well in traditional organizational settings. The method requires one-on-one or small-group interaction with a skilled facilitator. You cannot run it at scale across a company of five thousand people without significant infrastructure. If that's your constraint, you need a different approach — spaced repetition systems, microlearning modules, structured peer coaching circles. Those can build certain types of capability effectively. They just don't produce the same depth of behavioral change as deliberate friction. There's also a personality factor. Some people shut down completely under sustained productive struggle. They interpret the lack of immediate guidance as incompetence on their part, not as the intended method. I've seen this most often with high-performers who are accustomed to being good at everything quickly. For those individuals, you need to explicitly frame the difficulty as the point before they start, and you need to monitor their stress signals closely. If their cortisol levels are spiking — visible as rushing, irritability, or withdrawal — the exercise has gone too far too fast.
How to Start
Pick one capability. Just one. Define it in behavioral terms. Run a raw attempt scenario without any teaching. Time-box the struggle. Intervene with a hint, not an answer. Debrief with specific observations. Repeat with a varied condition. That's the full loop. It takes about twenty to thirty minutes per cycle, and you usually need three to five cycles before the behavior starts sticking. The reason this approach gets overlooked is that it looks like nothing is happening during the first half. No frameworks, no models, no handouts. People watching from the outside think the facilitator isn't doing their job. That's the point. The learning is happening inside the person, not in the materials being presented. Recognition of that fact is what separates people who use this method effectively from people who try it once, feel uncomfortable, and go back to the lecture model.
