The workshop was excellent. Genuinely. The facilitator was sharp, the frameworks were clean, the room was full of energy. People left inspired, notebooks full, resolutions made. And two weeks later, you cannot point to a single behavior that changed. The buzz is gone. The frameworks are in a drawer. The person is exactly who they were before, minus a day of work and a line in the budget.
Here is what happened. The development did not fail on delivery. It died in transit. It never survived the trip from the workshop back to the workflow, from the room where the ideas were safe and abstract to the desk where they were hard and real. And that short trip is where almost all development dies.
We design development for the room instead of the return. We optimize for the experience: the aha, the engagement scores, the warm applause for the speaker at the end. Which is exactly the wrong target, because a great workshop experience and a changed behavior are two entirely different products, and nearly every program is built to ship the first. The applause is the metric, the applause happens in the room, so the room is where all the effort goes.
Insight is not change. It is the feeling of change, and it expires.
Insight is cheap and perishable. It arrives with a rush that feels like transformation, and it is not. Real change is what happens on the twelfth ordinary Tuesday afterward, when the old pattern shows up under pressure and, this one time, something different happens instead. That moment never occurs in a workshop. It occurs weeks later, in the workflow, with no facilitator in the room and no energy in the air. And if nothing has been built to support it there, the insight quietly expires and the person reverts, not from any lack of will, but from a lack of scaffolding.
Development that survives is designed backward from the workflow, not forward from the workshop. The event is the smallest part of it. What matters is everything around the event: the practice, the reinforcement, the accountability, the repeated moments where the new behavior gets rehearsed under real pressure until it quietly becomes the default. You do not develop a person in a day. You develop them in the weeks after the day, inside a system that carries the insight home and keeps it alive long enough to harden into who they are.
A workshop is a spark. Sparks need something built to catch them, or they go out in seconds. Most organizations light the spark, admire how bright it is, and build nothing for it to catch on. Then they wonder why the fire never started.
So the real question is not whether your development is good. In the room, it probably is. The question is whether any of it is still alive on the desk a month later. If the honest answer is no, then you are not funding development. You are funding an event that leaves a development‑shaped feeling behind, and the two cost about the same while doing entirely different things.
Stop building the workshop. Start building what happens after it.