What Happens to Your Work After You Leave
Nobody tells you this when you start doing this work.
You spend years learning how to design programs, facilitate rooms, coach leaders through the hardest conversations of their professional lives. You get good at it. You build a reputation. Clients refer you to other clients. And somewhere in the middle of all of that, you start to notice a pattern that nobody in this field talks about out loud.
The best thing you can do for your clients is make yourself unnecessary.
I did not figure this out on my own. I had to be humbled into it.
I found out the way you usually find out about these things. Not directly. Through someone who knew someone.
About a decade ago, a former client — a biotech company where I had spent six months running a leadership development program — had put out a search for a new facilitator. Different firm. Fresh start. The program I built was being replaced.
I wish I could tell you I handled this gracefully. I did not. I refreshed LinkedIn approximately 10 times looking for context clues. I replayed every session in my head. I considered, briefly, sending a very calm and professional email that definitely would not have been either of those things.
Instead I sat with it. Which is what I tell my clients to do. It is easier advice to give than to take.
Here is what I eventually had to admit: I had built something that only worked when I was there.
The sessions had been good. The feedback was strong. Leaders were showing up differently in the room. By every visible measure, the work was working. And then my engagement ended, and apparently so did everything we had built together.
My first instinct was to make it about them. Budget constraints. Leadership turnover. The usual reasons organizations quietly abandon development work. All of those were probably true.
But the more honest answer was simpler. I had designed a program that lived in the sessions. The insight stayed in the room. The behavior change stopped at the door. When I left, the program left with me.
I had spent six months building something that dissolved the moment I stopped showing up. Which, if you think about it, is a very expensive way to change nothing.
There is a version of this work that is accidentally designed to keep you needed. You build something excellent. People rely on it. They rely on you to deliver it. The organization grows while you are there and contracts when you are not. Nobody intends this. It is just the path of least resistance. It also happens to be great for repeat business, which I am not proud to admit crossed my mind.
Designing for your own obsolescence is harder.
It requires more upfront work, more trust in the people you are developing, and a willingness to hand something over before it feels completely finished. It means accepting that someone else will deliver your program differently than you would. That they will adapt it, simplify parts of it, emphasize things you would not have emphasized. That watching this happen will be uncomfortable in a way that is difficult to explain to anyone who has not built something and then had to let it go.
But it is the only approach that actually serves the organization.
A study published in the Journal of Applied Behavioral Science found that leadership programs designed with explicit transfer mechanisms — internal facilitators, peer accountability structures, documented methodology — produced behavior change lasting an average of 14 months longer than programs without them. Same content. Fundamentally different architecture. The difference was not what got delivered. It was what got left behind.
Fourteen months. For the same program. Just designed differently.
After the biotech moment, I went back and looked at everything I had built for that engagement. The session materials were excellent. The facilitation was strong. And there was almost nothing designed to survive my departure.
No internal facilitator trained to run the next cohort. No measurement system for the HRBP to track behavior change at 60 and 90 days. No peer accountability structure to keep leaders connected after the sessions ended. No documentation of why the program worked, only what it did — which meant anyone who inherited it would be following a script without understanding the reasoning behind it.
I had built a program. I had not built infrastructure.
The distinction matters more than most practitioners want to admit. A deliverable is something you hand over when it is finished. Infrastructure is something the organization runs on after you are gone. They require completely different design thinking, and most of us are trained to build the former.
I eventually got this right — twice, in ways that stuck with me.
The first was with a global speaker organization. Three years coaching their talent, but I also built a methodology the internal team could use after I was gone. The diagnostic framework. The common patterns. The moments where most speakers need a specific kind of intervention. What I handed over was not a curriculum. It was a capability. People I never met were coached using something I built.
The second was with a technology company running a manager development program. Instead of facilitating every session myself, I spent the first two months training three internal HRBPs to co-facilitate alongside me. By month four they were running sessions independently. By the end of the engagement they had adapted the curriculum for their own context in ways I would not have thought to. The program they ran in year two was better than the one I had designed in year one. I had nothing to do with it. That felt exactly right.
That is the best possible outcome. It is also, if I am honest, a little terrifying. Watching something you built continue without you, knowing it will be done differently, knowing you cannot control it anymore. I find this uncomfortable every single time. I have also learned that the discomfort means I care, and that caring is actually the point.
Before I design anything now, I ask three questions I used to skip entirely.
●What needs to be true for this work to continue after I leave? This forces the sustainability conversation upfront rather than as an afterthought, which is where it usually lives and where it usually dies quietly while everyone pretends not to notice.
●Who inside this organization needs to understand this well enough to carry it forward? The answer changes everything about how you design. You build with them, not just for them. They stop being an audience and start being co-architects.
●What would success look like in two years, not two months? Satisfaction scores and completion rates tell you almost nothing about whether development work is holding. The real signal shows up later — in how a leader navigates the next hard situation, in whether the behavior change survived contact with real organizational pressure. This question also makes clients slightly uncomfortable, which I have come to think of as a good sign.
Here is the counterintuitive thing I have learned after fifteen years of this work.
The organizations that get the most from their development investments are not the ones that hired the best facilitators. They are the ones that hired facilitators committed to making themselves unnecessary.
When clients know your goal is genuinely their long-term capability and not your continued engagement, something shifts. They invest more. They take the work more seriously. They stop treating development as something being done to them and start treating it as something they are building together.
The work lasts because they own it. Not because you are still there holding it up.
I think about the biotech company sometimes. I do not know if the new facilitator built something that held. I hope they did — not in a gracious professional way but in a real way, because the leaders in that organization deserved work that lasted.
What I know is what I would do differently. Less time perfecting the sessions. More time building the organization's capacity to run without me. An internal facilitator trained from month one. A measurement system built before the program launched, not after. A deliberate plan to make myself progressively less necessary.
The goal I never told my clients is this: I want to leave every organization I work with more capable than I found it. Not more dependent on me. Not impressed by what I built. More capable. On their own. Without me.
That is harder to sell than a six-month program.
It is also the only thing worth building.
I work with leaders and organizations on building development that holds — not just while I am in the room, but long after. If this resonated, I would love to hear what it brought up for you.
