The Expertise Fortress

He'd been promoted three times in five years. Each time, the first thing he did was learn everything his new team knew — every system, every process, every edge case.

His direct reports joked about it. "He knows more about our jobs than we do."

He sat across from me with his hands flat on the table, fingers spread, as though he were steadying something. He'd been asked to describe what was going wrong with his team. He talked for twelve minutes about technical processes, regulatory timelines, stakeholder matrices. He described the system with surgical precision.

He did not mention himself once.

When I pointed this out, his fingers pressed harder into the table. "I'm not the problem," he said. "The team isn't stepping up."

...

I see this pattern in session after session. A leader arrives who built their career on knowing things. On being the person in the room with the answer. The one who could go deeper than anyone else, see further, hold more detail. That capacity earned them every promotion. It earned them the title. It earned them the respect of people who measure respect in competence.

And then the room changed. The job stopped being about knowing and started being about leading. But the identity didn't get the memo.

So the leader does what has always worked: they learn. They master their team's domains, one by one. They review every document. They attend every technical meeting. They carry the entire intellectual weight of the function on their own shoulders — not because they have to, but because putting it down feels like falling.

This is what I call the expertise fortress. A structure built from genuine competence that becomes the only place the leader feels safe. Inside the fortress, they are valuable. They are respected. They are needed. Outside it, there is a question they cannot yet face: what am I worth if I'm not the one who knows?

The fortress is not arrogance. The leaders who build it are often the most conscientious people in the organisation. They learn their team's jobs not from distrust but from a deep, unexamined belief that knowing is caring. That thoroughness is love. That if something fails and they didn't understand it completely, the failure is theirs.

The belief is invisible because it looks like a virtue. Across industries — pharma, tech, financial services — it arrives dressed as dedication. It sounds like "I just want to make sure we have the data." It feels like responsibility. It functions as a prison.

...

Here is what the fortress costs.

The team stops growing. When the leader carries the intellectual load, the team has no reason to develop their own. They bring every decision upward — not because they lack capability, but because the system has taught them that capability lives in one person. The leader who knows everything creates a team that knows nothing needs to change.

The leader cannot be promoted. The organisation looks at the function and sees a single point of dependency. Nobody can replace someone who has made themselves irreplaceable. The very strategy that was supposed to secure the career is the thing that caps it.

And underneath both of these, something quieter: the exhaustion of maintaining expertise that was never really about the work. It was about safety. About earning a seat at a table that was offered years ago and never fully accepted.

The leader I sat with that day — the one with his hands pressed flat on the table — eventually said something that changed the session. He said: "I think the reason they're not stepping up is because I haven't made room."

His shoulders dropped when he said it. Two inches, maybe. The kind of release you feel more than you see.

He didn't fix anything that day. He saw something. The fortress didn't disappear. But for the first time, he could see it as a structure he'd built — rather than the ground he was standing on.

The question isn't whether expertise served you. It did. Brilliantly. The question is whether you're still choosing it — or whether it's choosing you.

...

Related articles