Being indispensable sounds like a good career strategy.
If you're the only person who understands an important system, people need you. Your name comes up in meetings. When something breaks, somebody comes looking for you.
That feels a lot like job security and, for a while, it can even look like success. You have knowledge that nobody else has and the business would struggle without you.
But being needed for the same thing forever isn't security.
It's a trap.
The wrong kind of value
Early in my career, I wanted to be the person with the answer.
I learned the obscure parts of the system, remembered why strange decisions had been made and became good at fixing problems quickly. The more things came to me, the more useful I felt.
There was an obvious reward for it. Solving the problem myself was faster than explaining it to somebody else, and being the person who saved the day was satisfying.
So I kept doing it.
The trouble with becoming the answer to every question is that people keep asking you the questions. Your value becomes attached to a narrow set of responsibilities and you can't move far from them because the work doesn't move with you.
Being the only person who can do something makes you important, but only in the place where you're already standing.
Indispensable people get stuck
If a team can't manage without you, taking on a different role becomes difficult.
You may be ready to lead a larger team, start a new product or solve a more interesting problem. But somebody still needs to look after the system that only you understand.
The business has two choices. It can move you and accept the risk, or leave you where everything feels safe.
Safe usually wins.
This is how capable people become trapped by their own competence. They do a job so reliably that nobody can imagine somebody else doing it.
The problem isn't limited to promotions. Even holidays feel like work, only with nicer scenery. A day away produces a queue of questions. Every incident finds its way to you, even when you're no longer the right person to handle it.
You built job security and discovered that the job is now secured to you.
Knowledge needs somewhere to go
Teams are fragile when important knowledge lives inside one person's head.
It doesn't matter how talented that person is. They can be ill, leave the company or simply be unavailable when something goes wrong on a Sunday morning.
People sometimes call this the bus factor, which is a fairly grim way of asking how many people can disappear before the work stops. I prefer to imagine that they've all won the lottery and stopped answering Slack.
Either way, the problem is the same.
If one absence can stop the team, the knowledge hasn't been shared well enough.
Writing things down helps. A useful document can explain how a system works, how to release it and what to check when it fails. But documentation isn't enough on its own. A page nobody has used is only a theory that somebody else could do the work.
Knowledge becomes shared when another person has actually used it, made a decision with it and discovered which important detail you forgot to write down.
Teaching takes longer
Doing something yourself is usually quicker today.
You already know the context, understand the shortcuts and can avoid the mistakes. Explaining all of that to somebody else can make a one-hour task take an afternoon.
That makes teaching look inefficient.
But doing it yourself only completes the task once. Teaching somebody else increases the number of people who can complete every similar task that follows.
The first handover is slower. The next one is easier. Eventually, the question stops coming to you at all.
This requires more than showing somebody which buttons to press. They need to understand why the work is done that way, which parts matter and where they're allowed to make a different choice.
Instructions help somebody repeat your process. Context helps them deal with the situation you didn't predict.
The second is much more valuable.
Let somebody else own it
Sharing knowledge is difficult if you keep taking the work back.
I've seen leaders delegate a responsibility, then remain involved in every decision. They review every detail, answer every question and step in as soon as the new owner does something differently.
The task has moved, but the ownership hasn't.
If somebody needs your approval at every step, you haven't made yourself replaceable. You've created a longer route back to yourself.
Real handover means allowing another person to make decisions and live with the results. They may choose a different approach. They may take longer, miss something or make a mistake that you would have avoided.
That's uncomfortable, particularly when you know you could fix the problem in five minutes.
But rescuing them every time teaches both of you the wrong lesson. They learn that you'll eventually take over, and you learn that nobody else can be trusted.
Give them enough support to succeed, but leave enough space for the responsibility to become theirs.
A team should survive its leader
This matters even more in leadership.
A leader who makes every decision can look extremely valuable. They're involved in everything, everyone seeks their opinion and very little happens without them.
They're also the reason very little happens without them.
The job of a leader isn't to become the centre of the team. It's to build a team that can make good decisions when they aren't in the room.
That means sharing context before it's needed. It means letting other people lead meetings, handle difficult situations and build relationships across the business.
It also means giving away some of the work you enjoy.
Delegating administration is easy. Delegating meaningful work is harder because meaningful work is often where status, satisfaction and visibility come from.
But if you keep every interesting decision and hand over only the chores, nobody else develops and you remain essential for all the wrong reasons.
The clearest evidence of good leadership is often what happens when the leader isn't there.
Replaceable doesn't mean irrelevant
Making yourself replaceable can sound like volunteering to be removed.
If somebody else can do your job, why would the company still need you?
Because your value shouldn't depend on protecting a fixed collection of tasks.
The goal isn't to prove that anyone can replace everything you bring. It's to make sure the team isn't dependent on you continuing to perform the same responsibilities forever.
When somebody else can run the process, support the system or make the routine decisions, your time becomes available for a problem that still needs you.
Perhaps that means taking on a larger role. Perhaps it's a new product, a struggling team or the difficult piece of work that nobody has had time to understand.
And if there isn't another useful problem for you to solve, being the only person who knows an old system was never going to create one.
Hoarding knowledge can delay that truth. It can't change it.
Create room to move
The people who grow aren't always the ones who make themselves impossible to remove.
They're the ones who leave capable people behind them.
They explain what they know, write down what matters and give other people real chances to take responsibility. Each time they move on, the work continues and somebody else is stronger because they were there.
That creates trust.
You can give them a bigger problem because they won't cling to it forever. You can move them into a new area because they know how to make the old one safe. You can let them take a holiday without quietly planning to call them on the second day.
Making yourself replaceable isn't one grand handover before you leave. It's a habit.
Document the thing only you know. Invite somebody into the decision you usually make alone. Let another person handle the next incident while you stay close enough to help.
Then resist the urge to remain at the centre of it.
Being the only person who can do your current job may keep you in it.
Teaching somebody else how to do it creates somewhere for you to go next.
