The offsite was energising. The frameworks were sharp. Three weeks later, almost nothing has changed. This is the predictable arc of development delivered
The offsite was energising. The frameworks were sharp. Three weeks later, almost nothing has changed. This is the predictable arc of development delivered as an event: insight without an operating system to hold it. Capability that isn't wired into how decisions, reviews and handoffs actually run will always decay back to the old default — because the old default is the only thing that's structural.
The Event Trap converts development budget into a temporary mood. You pay for energy that fades, then pay again next year to re-create it — while the behaviours you actually wanted never become permanent. The recurring spend hides a recurring failure to change anything structural.
Development sticks only when it is wired into the operating system — the reviews, decisions and handoffs that run every week — rather than delivered as a moment. You don't program new behaviour into people for a day; you install it into how the work runs, so the new way becomes the path of least resistance.
What from your last leadership programme is still visibly changing how your team works today? For most organisations running the Event Trap, the honest answer is very little, which is the clearest sign the programme delivered insight without a system to hold it, and the old operating default reasserted itself once everyone was back at their desks.
Is 'training doesn't stick' actually backed by research, or is it just a feeling? It's well documented. McKinsey found only 11% of executives strongly agree their leadership-development interventions achieve and sustain results, and Gallup found only 23% of employees rated recent compliance/ethics-style training 'excellent,' with just 1 in 10 saying it changed how they actually work.
How much money is actually being spent on training that doesn't produce lasting change? A very large amount. Harvard Business Review has reported companies globally spend hundreds of billions of dollars a year on training, yet the learning routinely fails to change organisational performance because people revert to old habits once the programme ends.
What's the biggest practical obstacle CHROs report to making development actually work? Time. Gallup's 2025 research on employee development found 89% of CHROs cite time away from job responsibilities as the top obstacle. Development competes directly with the day job, and the day job usually wins by default.
Why does insight fade even when the workshop itself was genuinely good? Because a workshop changes intent, not infrastructure. The moment people return, the existing meetings, unspoken decision rights, and incentives reassert themselves, since they're the only thing that's actually structural, so insight without infrastructure always loses.
What does 'embedding over events' actually look like day to day? The new behaviour has to be load-bearing somewhere real: a decision review that now requires it, a standard that's checked, a ritual that reinforces it. That way the desired behaviour becomes the easiest way to get work done, not something people have to remember to do.
How do you actually measure whether development spend is working, beyond a satisfaction survey? The real test isn't how people felt during the programme; it's what's structurally different a quarter later: which decisions, meetings, or standards changed and stayed changed.
Is this something an internal L&D team can fix on their own? Often the diagnosis is easy for an internal team to see; the harder part is redesigning the operating rhythm itself while still running the business, which is usually where outside structure accelerates things rather than replaces the internal team's work.