I worked with a client for a long time. I’ll call him Tim. The kind of owner you don’t have to convince to take things seriously. He was already in it, already carrying weight, already making decisions that mattered. The business wasn’t broken, but it wasn’t free either.
You could feel where everything still came back to him, even if it didn’t look that way on the surface. That tension where growth is possible, but only if something fundamental changes.
We spent a lot of time inside that space. Not talking about growth in the abstract, but looking directly at what it would require. Where decisions were being held. Where people were waiting instead of moving. What would actually have to shift if the business was going to move past him instead of through him. There wasn’t anything that was hidden. He saw it, and he saw it quickly. He didn’t need a long explanation. He understood it as we were working through it, which is rare enough that you notice it when it happens.
That’s why what happened next didn’t fit the script I was used to running. He didn’t hesitate, and he didn’t stall. It becomes easy to drift back into old patterns but he didn’t need to be convinced of what was possible. He just made a decision. He took everything he had worked through and used it, but not in the direction I expected. He didn’t use it to build something bigger. He used it to step out. He designed his exit from the business with the same clarity we had been applying to scaling it.
It wasn’t reactionary or emotional. And Tim was not the kind of guy that gave up.
What he was doing was clean and intentional. It was aligned with what he actually wanted his life to look like, not just what the business could become. And it worked. There was nothing messy about it. No collapse, no scrambling, no last-minute correction. Just a decision followed all the way through.
And that’s where it got uncomfortable for me, because there wasn’t anything wrong with what he did. If anything, it was one of the clearest examples of someone making a decision from a place of ownership that I had seen in a long time. But it didn’t sit the way I expected it to. It didn’t feel like a clean win on my side of the table, even though everything about it said it should have been.
That situation with Tim didn’t feel new, and that is probably what stayed with me more than anything else. It would have been easier if it felt like a one-off, something unique to him or to that specific business, but it didn’t land that way. It felt familiar in a way that connected back to a lot of things I had already lived through and had already seen in other people’s businesses as well. I have spent enough time around centralized decision-making to understand what it does over time. I don’t need to theorize about it. I’ve watched what happens when everything meaningful finds its way back to one place, when decisions slow down not because people are incapable but because they are waiting, and when pressure builds in a way that is hard to explain until you are the one carrying it.
What I had not been as direct about was how close I still was to recreating that same pattern in a different form. It does not sit inside their org charts or their reporting structure, it’s in the way I was working with them.
I could see things clearly when I stepped into a business. Finding where decisions were getting stuck, where roles were blurred, where people were holding onto things longer than they should was where I excelled.
That work mattered and it created real movement. But I didn’t just hand that clarity over and step back from it. I stayed connected to it in a way that felt helpful in the moment. Close enough that the next layer of thinking often still came through me, even when the intention was to move ownership away from me. That doesn’t feel like control when you are in it. It feels like support. It feels like you are making things easier to move forward. It feels like you are protecting the progress that has already been made.
The problem is that progress can hide where ownership actually lives. I’ve seen meetings get better, decisions feel cleaner, and things that used to stall start moving again. That creates a sense that the work is landing the way it should, and it makes it easy to point to outcomes as proof that everything is working. I believed that for a long time. I believed that the clarity I was helping create was transferring in a way that would hold without me being there to reinforce it. Tim’s decision made me stop and look at that more closely, because he didn’t stay connected to me for the next step. He didn’t need me to interpret what came next or validate the direction he was taking. He took what he needed and moved forward without me in the middle of it, and that is where the mirror showed up whether I wanted it to or not.
If the goal is to build someone who can actually think, decide, and move without you, then the real question is not whether they can follow your thinking while you are there. The question is whether they can continue without it being routed back through you at all.
This is where it stops being about Tim, even though it would be much easier to leave it there and treat it like an isolated situation. A client made a clear decision, it didn’t follow the expected path, and it forced me to think about something differently. That version keeps everything contained. It lets me observe it without having to include myself in what actually changed. The problem is it didn’t stay contained. Once I let it sit for a while, it started connecting to things that had been there for years, just not lined up in a way that forced me to deal with them directly. I had already seen centralized leadership break people down over time. I had already seen what happens when everything routes back to one person and how that pressure builds in ways that are not obvious until it starts taking something from you. I had built a lot of my work around helping owners move out of that pattern. That part was real.
What I hadn’t been willing to look at as closely was how I was still sitting in a version of that same pattern, just from a different position. I told myself I was helping people think more clearly, and that’s still true. I could walk into a business and find the friction quickly, see where decisions were getting held, understand where people were waiting instead of moving, and help an owner work through what would actually need to change if they wanted something different. That created real movement and made things better. But I didn’t just hand that clarity over and remove myself from it. I stayed close to it. Close enough that the next layer of thinking often still came through me more than it should have, even when the intention was to build something that could operate without that dependency.
That doesn’t feel like control when you’re inside of it. It feels like support. It feels like you’re making things easier to move forward and protecting the progress that has already been made.
That’s the part I didn’t want to see clearly, because there is something in that position that is hard to walk away from. Being the one people come to when things matter feels like value. It feels like you are doing what you’re supposed to be doing. It feels like you are necessary to the outcome, and when the results are good it reinforces that belief. At the same time, there is a business behind that dynamic. We worked with companies that didn’t have internal capacity for this kind of thinking yet, and we filled that gap. That was real, but it also meant the longer we stayed relevant, the more stable our business became. That is not a moral statement, it’s just how it works. The tension shows up when you put that next to the idea of building owners who can actually operate without you, because those two things don’t naturally move in the same direction. If someone becomes the expert in their own business, if they can think, decide, and move without routing that thinking back through you, then they don’t need you in the same way anymore.
That’s where it becomes uncomfortable in a way that is hard to ignore once you see it. I can look back and see that I gave people a lot. I helped them move forward. I helped them clean up things that had been weighing on them for a long time. I helped them make better decisions. All of that is true.
But it is also true that I stayed close to that value in a way that kept me in the system longer than I should have been. It wasn’t every time, nor was it in some calculated or manipulative way, but enough that I can’t pretend the incentive was neutral.
And once that becomes clear, it changes how you see everything that came before it, because you can’t go back to calling it pure without ignoring the part that was always there.
That realization didn’t stay theoretical for very long, because once you see where the tension actually sits, it starts showing up everywhere you look. It wasn’t just Tim. It wasn’t just one client making a clean decision that didn’t match the direction I expected. It was the pattern behind how the work was structured and what it was actually producing over time. I had spent years inside a model that made sense on the surface. We connected with a client, helped them identify problems, built strategies, implemented changes, tracked progress, and then did it again. It created movement and results. It also kept the relationship going. And that last part is where it started to break down for me, because the continuation of the relationship was not always tied to the level of ownership being built inside the business.
That is a hard thing to sit with when you’ve built your identity around helping people move forward. There is nothing inherently wrong with staying connected to a client. There is value in long-term relationships and in continuing to refine and improve what has already been built. But that is not the same thing as needing to stay involved for the system to keep working.
When those two things start to blur, it becomes difficult to tell whether you are building independence or maintaining relevance.
I don’t think I asked that question directly enough while I was in it, because the work itself kept producing enough visible progress to justify the model. It’s easy to point to improved numbers, better structure, and clearer decision-making as proof that everything is aligned. It’s harder to step back and ask whether the business is becoming more capable without you, or just more functional with you.
That’s where the model stopped holding for me. It wasn’t that it didn’t work. It just didn’t produce what I said I cared about most.
I said I wanted owners who could operate without needing to route their thinking through someone else. I said I wanted teams that could move without waiting for a central point of control. I said I wanted businesses that didn’t depend on a single person to function.
And at the same time, I was operating inside a structure that still kept me close enough to influence the direction of that thinking in a way that made it harder for it to fully transfer. That contradiction is not something you can explain away once you see it clearly. It forces a decision.
And that decision isn’t comfortable, because it means letting go of something that has been working. It means stepping away from a model that produces consistent results and predictable income. It means accepting that the way you have been creating value is not aligned with the outcome you say you are trying to produce.
At some point this stops being something you can adjust around. That’s probably the cleanest way I can say it without turning it into something more polished than it actually felt. There wasn’t a moment where I sat down and decided to build something new. I didn’t have a whiteboard session with my team where everything came together and turned into a model. What happened was much simpler than that and a lot harder to avoid.
The way I had been working no longer held up against what I said I cared about, and once that gap was clear enough, continuing in the same way didn’t make sense anymore.
That doesn’t mean everything I had done before was wrong. It just meant it wasn’t complete in the way I thought it was. I had been helping people move forward. That part doesn’t disappear. But forward movement is not the same thing as ownership, and I had enough evidence at that point to know the difference mattered more than I had been treating it. Not in theory, but in how it actually plays out over time. If someone can only move forward cleanly when you are close to the thinking, then you haven’t really changed the structure that created the problem in the first place. You’ve improved it and made it more functional. But you haven’t removed the dependency that sits underneath it.
Once that became clear, the question stopped being “how do we make this better?” and became something else entirely. It shifted into whether the work itself needed to change in a more fundamental way. It was no longer about tactics or the delivery. The actual goal of what was being built. Because if the goal is for someone to become the kind of leader who can carry their business without routing everything back through a central point, then the process has to force that ownership to transfer. It can’t stay connected to the person who helped define it. It has to move away from them completely, or it isn’t actually complete.
That’s where everything started to point in the same direction, even if it didn’t feel organized at the time. The patterns I had seen in my own businesses, the pressure that comes from everything coming back to one place, the way clients moved when they had clarity but still stayed connected to the source of it, and the way Tim made a decision without needing that connection to stay intact. I saw that none of those things were separate anymore.
They were all showing the same thing from different angles.
You don’t create independent leaders by staying at the center of their thinking. You don’t remove dependency by improving the system that still depends on you. And you don’t build something sustainable by holding onto the part of the process that keeps you necessary.
That’s what Empowerment Design came out of. It’s not a concept that needed to be explained, it’s a direction that was already there once everything else stopped making sense in the way it used to. It wasn’t about building better systems for people. It was about making sure the systems didn’t need you in order to hold. It wasn’t about giving better answers. It was about removing the need for someone else to be the place those answers come from. And it wasn’t about scaling a business in the way I had been thinking about it before. It was about whether the person running that business was actually becoming the one who could carry it forward without being tied to anyone else’s thinking.
At some point this stops being something you can read and agree with, and it becomes something you recognize. Because it names something you’ve already felt and probably worked around in your own way. Most people don’t need someone to tell them that everything routes back to them more than it should. They already know it. They feel it in how often they get pulled into decisions that shouldn’t need them, in how frequently things slow down when they step away, in how much of the business still depends on their presence even when it looks like it’s running well.
The harder part is admitting what sits underneath that.
It’s not in the things that come back to you, but that you’ve played a role in creating that pattern, even when your intention was to build something different.
That’s not a comfortable place to sit, and it’s easy to move past it quickly by focusing on what needs to be fixed instead of what needs to change. Fixing things keeps you in the same position. It keeps you close to the work, close to the decisions, and close to the place where everything eventually lands. Changing it requires something else entirely, because it means you have to step out of being the center of how things move.
That doesn’t mean you step away from your business or stop being involved in what matters.
It means you stop being the place everything has to pass through in order to move.
That’s a different kind of leadership than most people have been taught, and it doesn’t feel as productive in the moment because things don’t move as quickly at first. It’s easier to step in, clean it up, and keep things moving the way you know they can. It’s harder to let something develop without you shaping every part of it, even when you know that’s what actually creates something that can hold.
If you’ve felt that tension before, you don’t need a definition of Empowerment Design. You already understand what it’s pointing to. It’s not about having better systems or cleaner strategy. It’s about whether the people inside the business, starting with you, are actually becoming the ones who can carry it forward without needing to route that thinking back through someone else. That’s where this leads whether you call it that or not.
If you want to go deeper into that, there’s more at LeadersEvolutionMembership.com.