The goal of every coaching relationship is to make yourself obsolete, and the leaders who can’t stand that are building dependents, not successors.
The straightest thing I can tell you about coaching, after thirty-four years of it, is this: if your people still need you in five years the same way they needed you on day one, you failed. You didn’t help them. You captured them. There’s a version of mentorship that looks like generosity from the outside and is actually a slow harvest of someone’s dependence, and the tell is simple, the relationship never gets less necessary. It just gets more comfortable for the person on top.
I want to be careful here, because this one is easy to get wrong in the noble direction. The leaders I’m describing aren’t villains. Most of them genuinely love their people. That’s exactly what makes it dangerous. The hero complex doesn’t show up wearing a hero complex. It shows up as being so good, so available, so indispensable that the people around you never have to develop the thing you keep doing for them. You feel like the most helpful person in the building. You’re actually the ceiling everyone keeps hitting.
The win is when they don’t call you back
The clearest moment this ever clicked for me was watching an athlete I’d coached for years stop needing me. Not dramatically, there was no falling out. He just got to a point where he’d ask me something and I’d realize he already knew the answer, he was checking his work against mine out of habit. And then one day he stopped checking. He made the call himself, the right call, the call I would have made, and he didn’t run it past me first.
A lot of coaches feel a small death in that moment. I’ve watched it. There’s a flinch when the student stops needing you, because a piece of your identity was wrapped up in being needed. I felt the flinch too. But underneath it, if you’re honest, that moment is the entire point. That’s the win. Not the dependence, the graduation. The job was never to be his answer forever. The job was to install the process that generates answers so deep into him that he becomes his own source. The day he stopped calling me was the day I’d done what I was actually there to do. Everything before that was just the work; that was the result.
Followers wait for instructions; founders generate them
Here’s the operational difference, and it’s not soft, you can measure it. A follower waits for the next instruction. A founder generates the next instruction. One needs the loop closed by someone above them; the other closes their own loop. And the kind of relationship you run determines which one you’re manufacturing, whether you mean to or not.
I see it on the gym floor constantly. There’s the lifter who needs me to tell him what to do every session, and after two years he still needs me to tell him what to do every session, and I have to be honest about my own role in that, if he’s still dependent, somewhere I trained the dependence, probably because being needed felt good. Then there’s the one I coached toward reading his own body, adjusting his own loads, knowing when to push and when to back off. That one becomes an operator of his own training. He doesn’t need me. He’ll come talk to me because he wants to, not because the wheels fall off without me, and that distinction is everything. One of those is a follower I made. The other is a founder I made. Same gym, same coach, completely different intent underneath.
I run my businesses the same way now, and it’s the harder discipline, not the easier one. It would be faster, most days, to just do the thing myself and keep my people waiting on me. Dependence is efficient in the short run and fatal in the long one. The whole point of building anyone is to build them past you.
Needing to be needed is just ego with a kind face
I’ll say the part that’s uncomfortable, because I had to say it to myself first. A leader who needs to be needed is serving his own ego and calling it service. The need is the giveaway. If some part of you can’t tolerate your people outgrowing you, if the graduation feels like a loss instead of the goal, then the relationship was never fully about them. It was about what their dependence did for you, and that’s worth being honest about even when it stings.
I spent years as an invisible architect, building systems that ran for brands that never put my name on the work. That experience burned the need-to-be-needed out of me, because I had no choice, the whole assignment was to build something that would keep working after I was gone and never knew my name. You can’t get your ego fed in that arrangement. There’s no one to need you. The work either stands on its own or it doesn’t, and the only satisfaction available is knowing it stands. That turned out to be the cleanest possible training for coaching people, because it forced me to find my reward in their independence instead of their reliance.
The same thing built the part of my life I’m proudest of. A family doesn’t get strong because the person at the center makes everyone dependent on him. It gets strong because everyone in it becomes more capable, more themselves, more able to stand without you, and you find your pride in their capability rather than their need for you. That’s built in private, over a long time, by deciding again and again that you’d rather raise founders than keep followers.
So here’s the question to sit with, and answer it honestly. Are your people getting more capable or more dependent? Are you building toward the day they don’t need you, or quietly arranging it so that day never comes? The first one costs you the feeling of being essential. The second one costs them their growth, and costs the world whatever they’d have built if you’d let them go. Build founders. Then have the grace to watch them found something without you in the frame.
I live my truth and I make myself useful, and the most useful thing I can do for anyone is make them no longer need me.