The Question That Ended My Corporate Career
Why I Left 18 Years of Leadership Development to Build Something Different
For eighteen years, I built leadership development programs for a living. Good ones, too. Thoughtful design, strong facilitation, and real investment from the organizations that hired me. And for eighteen years, I watched something quietly repeat itself: the energy of a great program would fade within months, and the same leadership problems would resurface almost exactly as they were before we started.
For a long time, I treated this as a problem I could eventually solve from the inside. Better content. Stronger reinforcement. More engaging delivery. I tried all of it alongside thousands of talented people in this field who care every bit as much as I do. The pattern held anyway.
I didn't leave corporate life because I stopped caring about the work. I left because a series of personal moments made it impossible to ignore how little the environments I was working in actually valued the people doing the work, myself included. Without going into details, there was a stretch of time when the personal cost of staying became too high to keep quietly absorbing. It's part of why, when I finally left, I knew I wasn't going back to a traditional corporate structure—not because I was angry at the industry, but because I had learned something I couldn't unlearn: no job should require choosing between showing up for the people you love and keeping your career intact.
That realization didn't hand me a business plan. It simply made staying impossible.
What if the problem was never the program?
What came next was slower and harder than I expected. I spent real time asking a question most people in my field don't let themselves sit with for very long: What if the problem was never the program? What if capable people had been delivering exactly the right content into organizations that had never built the structure to sustain it?
I also spent a long time observing the leadership development market before deciding to enter it. It's a crowded field. Nearly every company in it is offering some version of the same thing, and I didn't want to spend years building one more voice saying what everyone else was already saying. I waited until I had something that felt genuinely different—not a better program, but a different category entirely.
That became ClarityWorks Partners and Manager Performance Architecture™, the system I built around a simple distinction I couldn't stop seeing once I saw it: Training teaches people what good leadership looks like. It doesn't install the structure that consistently leads them there without someone standing over their shoulder to reinforce it. Organizations don't have a management training problem. They have a leadership architecture problem. Once I could name that clearly, I couldn't go back to solving it the old way.
Walking away from eighteen years of steady, respected work to build something that didn't exist yet was, honestly, terrifying. I didn't have a guarantee it would work. I had a pattern I'd watched repeat for nearly two decades, a conviction that there was a better answer, and a refusal to spend another year quietly managing the same problem instead of fixing it.
The First Work That Has Felt Like Mine
I'm now writing a book on this framework, due to launch on September 1, and working directly with organizations willing to be proof that consistency can be installed rather than hoped for. It's slower, harder work than building another training program would have been. It's also the first work in my career that has truly felt like mine—built from something I genuinely believe rather than something I inherited.
If there's one thing I'd want another woman standing at a similar edge to take from this, it's this: the moment you can finally name the real problem clearly—the one nobody else is naming quite the way you see it—is usually not the moment to keep waiting for better timing. It's the moment to start building.
