by A. Verdin | May 18, 2026 | 3 Min Read

The Perfect Training Program That Worked Until the Work Got Hard

ChatGPT Image May 18, 2026, 09_23_34 AM

Adam started to notice the same feedback coming up again and again about the new training. As the leader of L&D, he had been confident in the early feedback. But over time, something started to shift. First, a comment from a regional director that her managers were still avoiding the harder conversations. Followed by a note from a business leader who said he wasn’t seeing much difference in how decisions were being made. Then a comment from his VP that she wasn’t hearing much change in how managers were showing up. So, nothing dramatic, and nothing that directly contradicted the positive feedback the program had received. On paper, everything still looked strong. Completion rates were high. Assessment scores were solid. Participants could explain the framework and point to examples of how they had tried to apply it. If anything, it reinforced the idea that the program had landed the way it was supposed to.

But something wasn’t translating.

The more Adam replayed those conversations, the more he noticed that the gap wasn’t showing up in what people knew. It was showing up in what they did when the situation became uncomfortable, ambiguous, or high-stakes.

A manager trying to address tension between two high-performing team members who no longer trust each other. A leader deciding whether to escalate a risk that could delay a major initiative. A team pushing toward a deadline while key information keeps changing and no one is sure who owns the final call. These were the kinds of moments people moved through every day. And yet, they were also the moments where the framework seemed to disappear. Because understanding alone doesn’t translate when conditions feel harder than expected.

And that’s what made the pattern difficult to diagnose. The instinct in L&D is often to look for gaps in knowledge or clarity. If performance is inconsistent, the assumption is that people need more exposure to the concept, more practice, more reinforcement.

But that wasn’t what Adam was seeing.

The managers who struggled weren’t confused about what to do. They were navigating conditions that made doing it difficult. Time pressure, competing priorities, unclear expectations, and in some cases, real or perceived risk in acting differently. Those factors don’t show up in a competency model. They don’t sit neatly inside a framework. But they shape decisions in ways that content alone can’t account for.

Looking back, Adam realized the program had been designed around what leaders needed to understand, not around the situations where that understanding would be tested. And that distinction mattered more than he expected.

Because once you start from the moment instead of the model, different questions emerge. Not just what skills are important, but where those skills will be used, what will make those situations difficult, and what pressures will be present when someone has to decide how to act.

In one case, it meant recognizing that a feedback conversation wasn’t just about structure or clarity, but about navigating the tension between performance expectations and the risk of damaging a relationship. In another, it meant acknowledging that pushing back on a decision required more than confidence in the framework; it required an understanding of the political and organizational dynamics surrounding that decision. And it’s those nuances that need to be part of the design, because they are part of the work.

At Unboxed, this is where the approach shifts from mapping competencies to mapping moments. Instead of starting with a list of skills, the focus moves to identifying where performance is breaking down and what those situations actually look like. From there, the conditions surrounding those moments become clearer, and the design can account for the pressures that shape behavior in real time. It’s a more grounded way of thinking about capability. And it tends to surface gaps that wouldn’t show up otherwise.

Because knowing what to do is rarely the constraint. Applying it, when the moment arrives, is. And if the design doesn’t start there, it’s easy to miss the moment that matters most.

More articles like this one