9. Develop People Until They No Longer Need You¶
Once the team exists and the standard is held, the next work is developing people into judgment. Care and standards keep the team intact. Development is how the team grows past needing you.
I am not going to pretend the motivation was purely generous.
I wanted the strongest team. Partly for the mission. Partly for me. Having sharp people around me made my own work better, made my own results better, made me look better. The development started from that impulse, not from a sense of managerial duty.
That is the honest starting point.
I am writing it down because if I skip it, the rest of the chapter will sound like a virtue story. It is not a virtue story. It is a story about a leader who began by wanting to own someone's growth and ended by realizing the growth was no longer his to own.
There was a designer on the team. UX-adjacent role. Strong instincts, still rough on the edges where instinct meets stakeholder pressure.
The early working sessions were arguments.
Healthy ones. Not shouting. Just two people pushing on the same UX decision from different angles, neither one folding. We would argue about a flow, argue about a placement, argue about what the user would actually do versus what the spec said the user should do. We would not reach a clean conclusion.
At that point, I had a choice. Pull rank and tell him what to ship. Or let him execute the version he was defending.
I let him execute his version.
Not out of generosity. Because I was watching for something.
Sometimes his version worked. Sometimes it did not. When it did not, the failure showed up in a way he could see — a stakeholder pushed back, a metric moved the wrong direction, a downstream team flagged something he had missed. The failure was small. Bounded. Visible to him.
Before the failure caught up further, I would step in. Show him what I had seen earlier in the argument that he had not. Let him fix it.
Then we would argue about the next thing.
That loop is the method. Argue. Give authority. Let him fail small. Catch before lasting damage.
The lesson was not told. It was felt. He had to feel the consequence of his own decision in a real situation before the correction would internalize. If I had simply told him the answer in the argument, he would have executed my answer and learned nothing. He would have learned compliance. Compliance is not development.
The catch is the part that gets missed when this method is described casually. The catch is real. The catch is calibrated. The exposure is to consequence, not to lasting damage. Without the catch, the method is not development. It is just letting people drown to teach a lesson, which is cruelty dressed up as coaching.
Somewhere in there, I started running a quiet check on myself.
Not a formal review. A weekly habit of noticing. Roughly: does this person still need me here?
In the early phase, the answer was yes. Things would happen and I would interfere early. Catch a stakeholder conversation before it slipped. Sit in a review and steer the framing. Notice a pattern in his work and surface it before it became his pattern.
Then one week I noticed I had stopped interfering early. I had started interfering late. He was handling the first reaction himself. By the time I came in, the situation was already partway through being managed — by him, not by me.
This was not a decision I had made. I had not sat down and said, now I will pull back. The pulling back happened because there was less to catch. He was catching things himself.
A few months later, I noticed I had stopped interfering at all.
The signal was not dramatic. No promotion announcement. No formal handover.
A stakeholder conflict came up — the kind that would have pulled me in earlier. He handled the conversation himself, made the trade-off, and came back with the outcome instead of the panic.
Then a crisis moment followed. Again, the old pattern would have been escalation first, judgment second. This time he contained it, made the first call, and reported what had been done.
That was when I realized the loop had moved.
He was no longer running the work and asking me to validate it. He was running the work.
I did not plan a three-stage exit. I noticed the pattern after the fact.
That is the honest version of how it worked. The ladder was not a curriculum I designed. It was a description of what I saw when I paid attention each week.
The Interfere Early → Interfere Late → Don't Interfere Ladder
A weekly habit of noticing, not a planned curriculum. Each shift is a real signal.
Stage 1 — Interfere Early.
The leader is catching issues quickly, staying close. The person is producing work but the judgment around the work is still being shaped. This is the highest-touch phase. Argue, give authority, let fail small, catch before damage.
Stage 2 — Interfere Late.
The leader notices that the first reaction is no longer the leader's. The person is handling the initial response themselves. The leader comes in further along, with less to correct. This shift is not a decision. It is a signal that something has internalized.
Stage 3 — Don't Interfere.
The leader notices there is nothing left to catch. Stakeholder communication, conflict resolution, crisis response — all happening without the leader. The person is running solo.
The ladder is descriptive, not prescriptive. The leader does not plan the withdrawal. The leader notices when the person no longer needs them at that stage, then lets go of that stage and watches the next one.
The cadence that feeds the ladder is a weekly mental check. One question. Does this person still need me here? That is enough.
The endpoint was quiet.
He became independent. Strong. Capable of his own decisions, his own relationships with stakeholders, his own responses to pressure. The development did not trap me into a permanent coaching relationship. It multiplied — there was now another person in the room who could carry the work without me in it.
The moment I realized I was not needed anymore, I expected to feel something. Some pang of being displaced. Mostly I just felt it was right.
The ego that had started the development had let go of the ownership somewhere along the way. I did not notice the release as it happened. I noticed it after — the same way I had noticed the ladder shifts after.
There was no ceremony. No announcement. He just stopped needing me in the chair beside him, and that is how I knew it had worked.
What bad leadership usually does¶
There are two defaults, both common, both real.
The first is the bottleneck leader. The leader who gives people tasks but keeps the thinking for themselves. Every real decision routes back to the top. People learn to execute. They do not learn to own. The leader feels needed, which is the trap, because feeling needed is easy to confuse with being trusted.
Reliance is not trust. Reliance is dependency. Trust is what makes reliance unnecessary.
The second is the over-protecting leader. The leader who catches every mistake before it lands. No failure, no consequence, no lesson. People stay technically correct and developmentally flat. Their work product is clean. Their judgment is untested.
The line between catching before lasting damage — which is the method — and catching before any discomfort — which is the trap — is thin and easy to cross. The first builds judgment. The second prevents it. Removing the consequence removes the lesson.
Both defaults look like leadership from the outside. Both feel like leadership from the inside. Neither develops anyone.
The principle¶
Leadership is multiplication, not dependency.
A leader who is still needed at every stage has not developed anyone. A leader whose people grow past the leader's involvement has multiplied.
Why it matters¶
If everyone needs the leader for every decision, the leader has built a bottleneck. The team's ceiling becomes the leader's bandwidth. Growth stops at the leader's calendar.
If the leader catches every mistake before it lands, the team becomes a set of well-supervised executors. Their work is fine. Their judgment never matures. The first time the leader is unavailable, the work falls apart.
If the leader develops people deliberately — argument, authority, small failure, catch before damage, weekly check, descending interference — the team gains people who can carry the work without the leader in the chair. The organization compounds. The leader is freed to work on the next thing, not because the leader walked away, but because the work no longer requires them.
The proof is what happens when the leader is not in the room.
What better leadership looks like¶
A leader who is honest about the impulse — wanting strong people around them — and lets that impulse turn into real development instead of staying as personal advantage.
A leader who argues with people instead of dictating to them, and who is willing to let the unresolved argument become an executed decision belonging to someone else.
A leader who gives authority for real, not as theater. Authority that includes the right to be wrong in a contained way.
A leader who catches the failure before lasting damage, and only before lasting damage. Not before discomfort. Not before learning.
A leader who runs a weekly check on themselves — does this person still need me here? — and who is willing to read the answer honestly even when the answer is uncomfortable.
A leader whose ego started the development and whose discipline finished it.
A note on the trap I was watching for¶
I have not walked into the dependency trap myself. Not yet. But I have seen it from outside, and the shape is clear enough to name.
The leader who interferes too long. Who catches every mistake before it lands. Who keeps the person dependent because independence would feel like loss. Who develops a portfolio of protégés who all still need the leader to validate their work, years in.
That leader is not developing anyone. That leader is building a mirror.
I am writing this down because the method in this chapter has a failure mode, and the failure mode is the leader who cannot let go of the catching. The weekly check is the protection. If the answer to does this person still need me here? keeps being yes for too long without changing, the question is no longer about the person. It is about the leader.
I have not had this bite me. I am writing it as the trap I am watching for, not the trap I have lived through. The honesty matters more than the completeness.
Simple rules¶
- Be honest about why you are developing someone. Ego and mission can both be in the room. Ego cannot stay in the chair.
- Argue with people on real decisions. Do not pull rank when the disagreement is about judgment, not standard.
- Give authority for real. Authority without the right to execute is not authority.
- Let people fail small. Catch before lasting damage, not before discomfort.
- Run a weekly mental check on each person you are developing. One question. Does this person still need me here?
- Read the interference ladder as a signal, not a plan. Early, late, none — each shift means something has internalized.
- The endpoint is quiet. No ceremony. The person stops needing you, and that is how you know it worked.
Reflection questions¶
- Am I developing this person, or am I keeping them close because being needed feels good?
- When we disagree on a real decision, am I willing to let them execute their version?
- When they fail, am I catching before lasting damage, or before any discomfort?
- Does this person still need me at the stage I am still showing up at?
- What stage of the interference ladder am I actually on with each person on my team?
- If I left tomorrow, whose work would still hold?
- Am I confusing reliance with trust?
Reminder¶
Leadership is multiplication, not dependency.
The best proof of leadership is when people become stronger after working with you, and the quietest proof is when they stop needing you to keep being strong.
Be useful for as long as the person needs you.
Let go cleanly when they do not.