I've never tried to keep someone on my team.

That probably sounds wrong. Maybe even irresponsible. If you've spent any time in a leadership role, you've likely sat through conversations about retention strategies, engagement surveys, and all the things organizations do to prevent their best people from walking out the door.

I've sat through those conversations, too.

And I've always believed they're asking the wrong question.

The question isn't how do we keep our best people. The question is, how do we develop them so completely, so genuinely, so deliberately that staying feels like the best possible next step for their career? And when it doesn't, when the right next step takes them somewhere else, how do we send them there with everything they need to succeed?

That's a different philosophy. And it changes everything about how you lead.

The belief I've carried for 23 years

My job as a manager has always been simple, even when the work wasn't.

Develop every person on my team until they're ready for what's next.

What's next might be a bigger role on my team. It might be a promotion inside the business. It might be an opportunity at another company entirely. And I've always been genuinely okay with all three outcomes because in every case, I did my job.

I call this The Developer's Mindset. And it's the single most important thing I've learned in 23 years of leading people.

Not because it's generous, though I believe it is. Not because it's the right thing to do, though I believe that too.

Because it's the most effective management philosophy I've ever encountered. And I've seen what happens to teams and careers on both sides of it.

💡The Vault Insight: Development isn't a retention strategy. It's a responsibility. And the managers who treat it that way build the most loyal, highest-performing teams — even when their best people eventually leave.

What most managers get backwards

Most managers develop people just enough to keep them performing in their current seat.

They give stretch assignments to prevent boredom. They have development conversations when someone signals they're looking elsewhere. They invest in people reactively, when retention is at risk, rather than proactively, as a fundamental expression of what leadership means.

That's development as a defensive tool. And it produces defensive results.

The people who benefit from it know, on some level, that their development is contingent on their willingness to stay. Which means it never feels entirely genuine. Which means it never produces the kind of loyalty that actually keeps great people around.

The Developer's Mindset runs in exactly the opposite direction.

You develop people not because you're afraid of losing them. You develop them because it's your job. Because they trusted you with a significant portion of their professional lives and your responsibility, your obligation is to return them to the world more capable, more confident, and more ready for what comes next than when they arrived.

That's a completely different contract. And people can feel the difference.

Here's something almost nobody talks about

In 23 years of managing people, I've noticed something consistent enough that I now treat it as a universal truth.

Almost every employee, at every level, wants to grow.

Not just the high performers. Not just the ambitious ones. Not just the people who tell you directly that they want to move up. Almost everyone sitting across from you in a one-on-one has some version of the same underlying desire: they want to advance, they want to earn more, they want to become more valuable, and they want to feel like their career is moving in the right direction.

What most of them don't have is clarity on what that actually requires.

They don't know what the next level looks like from where they're standing. They don't know what skills they need to develop, what behaviors they need to demonstrate, or what the person making the promotion decision is actually looking for. They're working hard, doing their jobs, hoping someone notices, and quietly wondering why the path forward feels so unclear.

That ambiguity is expensive. It breeds frustration, disengagement, and eventually departure. And in most cases it's entirely preventable.

Here's where I believe a manager's responsibility becomes explicit: it is your job to define what growth looks like for each person on your team. Not in vague terms. Not in the language of annual review forms and competency frameworks. In specific, honest, actionable terms that give each person a real picture of what they need to do to earn what they want.

That means setting a high bar and being clear about where it is. It means telling someone directly what they're doing well and exactly what's standing between them and the next level. It means being honest even when the honest answer is hard to hear, because the alternative, letting someone spend another year working without a clear target, is a far greater disservice than a difficult conversation.

Most managers avoid this because it requires two things that are genuinely uncomfortable. First, you have to define the standard clearly enough to articulate it. That's harder than it sounds. Second, you have to hold people to it honestly. That's harder still.

But here's what I've learned. When you do both of those things consistently, something remarkable happens. The people who can rise to the standard do. The people who can't, but want to, start closing the gap faster than you expected. And everyone on the team understands, concretely and specifically, what great looks like and where they stand relative to it.

That clarity is a gift. Most people never get it from a manager. The ones who do rarely forget it.

What happens when you operate this way

I want to be honest about something.

Not everyone you develop will stay. Some of your best people, the ones you invested the most in, the ones who grew the fastest under your leadership, will take that growth somewhere else.

That used to be a harder thing for managers to accept than it is for me now. I've watched it happen enough times to know what comes next.

Every person you develop and send into the world becomes a permanent advocate for you, your team, and your brand. They send you their best people when you're hiring. They refer business to your organization. They speak well of you in rooms you'll never be in. They become walking proof of what kind of leader you are because the career you helped build is visible to everyone who knows them.

I've hired people who worked for managers I developed years earlier. I've won business from leaders I helped grow. I've built teams faster than anyone thought possible because former direct reports sent me the best people they knew, people they trusted me with precisely because I had trusted them.

None of that happens if you develop people only enough to keep them in the seat.

All of it happens when you develop them for what's next and mean it.

The conversation most managers never have

Here's what The Developer's Mindset looks like in practice.

It starts with a conversation most managers never have, not because it's hard, but because it genuinely never occurs to them.

Sit down with each person on your team and ask them directly: where do you want to go? Not what do you want to do in this role. Where do you want to go. What does your career look like in three years, five years, ten? What kind of leader do you want to become? What are the skills, experiences, and opportunities you need to get there?

And then, this is the part that separates the managers who mean it from the ones who don't, actually build toward those answers. Create the stretch opportunities that move each person toward where they're trying to go, not just toward what the current role needs. Make introductions. Advocate for them in rooms they're not in. Give them visibility, feedback, and sponsorship that serves their career, not just your immediate team needs.

That conversation changes the dynamic of every subsequent interaction. Because now your direct reports know, concretely and specifically, that you are invested in where they're going. Not just in what they can do for you right now.

That's loyalty you can't manufacture any other way.

A word about the ones who leave

The best person I ever developed left my team for an opportunity I couldn't match.

I was proud of them the day they told me. I was genuinely happy for them. And I told them both things directly because they were both true.

That person has sent me three exceptional candidates over the years since. They've referred two clients to businesses I was part of. They've spoken about our time working together in ways that have opened doors I didn't even know existed.

The return on that investment has been extraordinary and completely invisible on any retention dashboard.

The managers who try to hold on to their best people because they're afraid of what happens without them build teams that are fragile, dependent, and ultimately average. Because the best people, the ones with real options, eventually leave anyway. They just leave later, with less goodwill, and with less reason to become advocates on the other side.

The managers who develop people deliberately, generously, and without conditions build something entirely different. They build a reputation that precedes them. A network that compounds. A legacy that outlasts every team they've ever led.

The question worth sitting with

If every person currently on your team left tomorrow and built remarkable careers somewhere else, would they say you were the reason?

Would they point to your leadership as the thing that changed their trajectory?

Would they send you their best people, refer you business, and speak about what it meant to work for you?

That's the standard The Developer's Mindset holds you to.

Not how long people stay. But what they become and whether you had anything to do with it.

Your job isn't to keep your best people.

It's to make them ready for what's next.

And if you do that well enough, staying will usually feel like the best option anyway.

—Sean McGinnis, 2X President, CMO, COO & EOS integrator