The Leadership Bottleneck


The Leadership Bottleneck

Why your best people might be blocking your next best people


Ten months into running a veterinary teaching hospital, I kept noticing something I couldn't quite put words to.

On paper, things looked fine. Every service had a leader. Nobody was on fire. The trains were running close enough to on time that most people wouldn't notice. We had stability.

What we had actually built was dependence.

We were leaning on a small group of talented, battle-tested people to hold important roles with no real plan for what came after them. I wrote it down at some point: we may have accidentally designed a system that traps our best people in roles they were never meant to hold forever.

To understand the problem, you have to understand the environment. A veterinary teaching hospital is not just a hospital. It is a clinical enterprise, a teaching institution, a research operation, a client-facing service organization, and on certain days, a group therapy session with billing codes.

Leadership does not live cleanly on an org chart. It lives inside the services — internal medicine, surgery, cardiology, oncology, anesthesia, emergency and critical care, radiology, dermatology, and every other specialty that makes the place run. Each service has its own rhythm, its own culture, its own long institutional memory, and its own particular brand of pressure.

Service leaders build schedules months out, trying to coordinate the calendars of specialists who guard their time like it's a nonrenewable resource. They run meetings where a routine equipment decision can spiral into a philosophical debate about the future of veterinary medicine. They fight for resources in hospital-wide conversations where everyone else is also making a passionate case for their own team.

And that is all on top of their actual job. Seeing cases. Teaching students. Mentoring residents and interns. Supporting staff. Trying to have something left over when they get home.

These are not the people you worry about. These are the people you count on.

That is exactly where the trouble starts.

When I looked closely at our structure, I found leaders who had been in their roles for many years. In some cases, more than a decade. A few even longer.

They were not there because nobody noticed them. They were there because everyone depended on them.

They knew the history. They knew which process existed because of a blowup from twelve years ago. They knew which meeting actually mattered and which was mostly ceremonial theater with snacks. They knew how to keep things moving when the system got heavy. By most measures, they were excellent.

That was the trap.

When someone does a complex leadership job extremely well, organizations tend to do the same thing: they stop touching it. The unspoken message becomes, "She has that handled," or "He's the only one who really understands how that works," or "If we move that person, things might fall apart."

That might be true for a season. If it stays true forever, you have a problem.

Over time, the role becomes part of that person's identity. They are no longer simply leading the service — in the eyes of the organization, they become the service. The institution quietly stops imagining anyone else in that seat. The leader may stop imagining themselves outside of it. And the people coming up behind them stop seeing any realistic path in.

That is the leadership bottleneck.

It is not usually created by selfish leaders. It is created by successful ones. That is what makes it hard.

When a leader is struggling, the problem is at least visible. It may still require more meetings than any reasonable human should endure, but everyone can see it. When a leader is doing good work, the problem is quiet. No dramatic failure. No warning light. No obvious moment where everyone agrees something has to change.

The cost shows up slowly. New leaders don't develop. Veteran leaders get worn down. Fresh thinking waits outside the room. The organization starts running on memory instead of building real capability.

Only a few doors down from some of these long-serving leaders were people who were ready for more. Not ready to run everything tomorrow. Not necessarily asking for a title. But ready.

In academic medicine, these tend to be faculty somewhere in that five-to-seven-year window. Enough experience to understand the work, enough credibility to move people, enough curiosity to ask why things are done the way they are. They see patterns. They take ownership. They have opinions not just about their own caseload but about how the whole service could work better.

You can usually spot them. Students and house officers look to them when things go sideways. Staff trusts them. Colleagues don't always agree with them — this is academic medicine, and universal agreement would probably violate several institutional policies — but people listen when they talk.

The question those people are quietly asking is rarely, "Can I have a title?"

It is usually something more basic.

Is there a path here?

In a healthy system, they see a horizon. Not a guarantee. Not a promise that every role will be theirs. Just a believable direction where leadership is something you can learn, practice, and grow into over time.

In a bottleneck, they see a wall.

A small number of important roles occupied indefinitely by people performing well and likely to stay. That creates a strange kind of organizational waiting room. People can be patient for a while. But patience without any real possibility eventually turns into something else, and that something else usually walks out the door with a letter of resignation.

Once I could name the problem clearly, the answer was not to redesign the people. It was to redesign the roles.

I was not trying to signal that long-serving leaders had done something wrong. Most of them had done something close to heroic — holding complicated systems together with experience, relationships, and professional grit. The question was never, "How do we move them out?" It was, "How do we build something that does not depend entirely on any one person?"

The answer we moved toward was simple in concept and messy in execution: defined leadership terms with the option to renew. Three-year terms. Actual written role descriptions so the position meant something more specific than "keep doing what you've always done." Transparent selection. Built-in review so there was a natural stopping point for honest reflection.

At the end of a term, the decision becomes intentional. Renew. Rotate. Transition. Figure out together how that person contributes going forward. That is very different from letting a role go on indefinitely because nobody wants to have the conversation.

The reactions were predictable, and most of them were fair.

Some leaders were relieved. A few had been looking for a dignified way to step back but didn't want to look like they were abandoning their service. Others were cautious, wondering if this was a polite way of saying we wanted them gone. Some were worried about what happened to their teams if they were no longer the one holding everything together.

Those were reasonable concerns.

What I figured out quickly was that how we framed the change mattered as much as the change itself. This was not about churn or cycling people out or chasing newness for its own sake. It was about treating leadership as a season of contribution, not a life sentence. One person should not have to carry a role forever for the system to function. Capable people need real opportunities before a crisis forces the issue. Current leaders should help shape what comes next, not get surprised by it.

That framing did not eliminate every worry. Nothing does. But it made the whole thing feel more honest.

Nine months later, what interests me most is not the structural change. It is the human one.

Some veteran leaders have moved from being the sole carrier of a service to something closer to a multiplier. They did not disappear when their terms ended or when transition conversations started. Some shifted into mentorship and advisory roles — still close to the work, still bringing what they know, but no longer the only ones holding it.

The new leaders stepping in are asking different questions. Why do we schedule this way? Why are certain caseload patterns treated as permanent? Why do some processes feel built around a problem from fifteen years ago rather than what we actually need now? Why do some training experiences feel more like endurance events than learning?

Not every question leads to immediate change, and that is fine. Some old ways exist for good reasons. Some new ideas need refinement. Some proposals need to survive contact with a budget, which is where many good ideas go to become slightly less good.

But the questions are being asked. That alone tells me something has opened up.

The problem was never that excellent people were in leadership. Every organization needs excellent people in leadership.

The problem was that our system did not give some of them a clean way out, or give others a clear enough way in.

Without that, excellence becomes a quiet obligation. Veteran leaders feel trapped by their own competence. People who are ready feel stuck behind something they cannot see around. The organization looks stable and is actually getting more fragile by the year.

If you lead anything complex, it is worth asking where your stability is actually coming from. If the honest answer is a small group of people doing the same hard jobs for a long time, you may not have solved your leadership problem. You may have just put it off.

The goal is not to move your best people out. The goal is to build something that does not fall apart without them at the center of it — and where they are not, without meaning to, standing in the doorway of whoever comes next.

Depending on good leaders keeps today running.

Developing new ones protects everything after that.

Most organizations are a lot better at the first one than the second.