I Made My People Good Enough to Quit

A message arrived a few weeks ago from someone who worked for me years ago. No agenda in it. He runs the team he used to sit in now, we have not shared an employer for a long time, and he wanted to show me a thing he is building. We went back and forth about it for an hour and barely talked about work at all.

This happens fairly regularly, from different people, and it is the single thing about my career I am most quietly pleased about. Which is a strange sentence, because none of it appears on any CV.

For years I ran teams on a principle that sounds wrong when you say it out loud. Make people good enough to quit. It was the best way I ever found to keep them.

Retention Is Usually Managed as Flight Risk

Look at how keeping people actually gets discussed in most companies. Compensation bands. Flight risk in the talent review. Counter offers. Retention bonuses for the ones you cannot afford to lose.

All of it treats a person leaving as a leak to be plugged. And the quiet logic underneath is that someone who becomes too capable becomes too portable, so the safest employee is one who is growing at roughly the speed of the org chart and no faster.

Nobody says this. Plenty of managers act on it. I have watched good leaders keep a strong person slightly boxed in, not out of malice, just because the alternative was frightening and the incentives did not reward it.

The trouble is it does not work. People can feel the ceiling long before anyone names it, and a person who has stopped growing does not stay loyal. They stay a while, and then they go, and they go bitter.

Hand Over the Thing They Are Better At Than You

The mechanic is simple and slightly uncomfortable. You find the one thing somebody is genuinely better at than you are, and you give it away.

Not the task. The call. Delegating work is easy and everybody does it. Delegating the decision, including the right to make it differently than you would have, is the part that actually grows a person, and it is the part most of us hold onto because our own reputation is attached to the outcome.

I also pushed context outward as far as it would go, which is why I used to bring backend developers into customer interviews rather than handing them a ticket. Once the problem lives in someone's head instead of in a description, they start making better decisions than the ones you would have specified for them. That is the entire mechanism. Give someone the reasoning and they can decide. Give them the conclusion and they can only execute.

People notice being built up like that. It is not subtle. They stay because they are growing, and growth is a much stronger reason to stay than a retention bonus.

What a Team Without This Actually Costs

Here is where it stops being a people topic and becomes a product topic.

If you are the only person on your team who can make the real calls, you have not built a strong team with a strong leader. You have built a product strategy with one point of failure, and the point of failure is you.

I have seen what that looks like from the inside. Everything routes through one person. Decisions queue behind their calendar. Nobody below them develops judgment, because judgment develops by making calls and being wrong sometimes, and they are never allowed to. Then that person goes on holiday and the whole product management process discovers it was a single-threaded thing wearing a team costume.

A team where only one person can decide is not a team. It is a queue.

And the reverse is what surprised me. Every time I gave a decision away properly, my own capacity went up more than the handover cost. Not because I had offloaded work. Because I stopped being consulted about things I had no better information on than the person in front of me.

The Measurement Nobody Has

None of this shows up in the systems companies actually use to evaluate leadership.

A performance review measures what a person produced inside the box you gave them, in the period you defined, against goals somebody wrote in January. It has no field for whether the people around them got better. It certainly has no field for whether they will still be around in five years, when there is nothing left to gain from the relationship.

That last one is the only real test I have found. Do people come back to you when you are not their manager, not a reference they need, not a name on the same payroll. When there is nothing in it for them at all.

I cannot prove that is a leadership metric. I only know it is the one that makes me happiest, more than most things I have shipped, because it is the only evidence I have that the way I led held up after I stopped being in the room to enforce it.

The Part I Miss

Right now it is just me. No team to grow, no one to hand a decision to, nobody who is better than me at something so that I can get out of their way. I build, I decide, I am wrong, I fix it, and there is no one across the desk asking the question that would have saved me two days.

I expected to miss the collaboration. I did not expect to miss the growing part this much. Watching somebody get good at something up close, and knowing you had a small hand in it, turns out to be the thing I would most like to do again.

So if you lead a product team at the moment, one question, and it is not a comfortable one.

Of the people who reported to you three years ago, how many would still send you a message with nothing attached to it?