There’s a strange thing that can happen when you become the person who can handle almost anything.
People stop noticing that you’re handling almost everything.
You solve the problem before it becomes a bigger problem.
You remember the thing everyone else forgot.
You fill the gap because leaving it open will create more work later.
You answer the question.
And when you don’t know the answer, you figure it out.
Eventually, everything just… works.
That should be a good thing.
And mostly, it is.
But there’s a downside to being consistently competent that we don’t talk about very often:
Competence can become invisible.
When “handled” becomes the expectation
Think about all the work that gets noticed in an organization.
A deadline gets missed. People notice.
A customer gets upset. People notice.
A mistake costs money. People definitely notice.
But what about the person who catches the mistake before it costs anything?
Or notices the deadline slipping and quietly gets things back on track?
Or answers the question that keeps five other people moving?
There’s no crisis. No meeting. No flashing red light.
The problem simply disappears.
Do that often enough and something interesting happens.
People stop seeing the problems you’re solving.
They simply experience an environment where those problems don’t seem to exist.
I’ve been thinking about this a lot lately because I’m fortunate to work somewhere I genuinely care about, doing work I genuinely enjoy. I have a tremendous amount of trust and autonomy, and I don’t take either for granted.
At the same time, I’ve realized that when you’re the person who naturally steps into the gaps, eventually those gaps can disappear from everyone else’s view.
Including your own.
You stop thinking:
I just solved a fairly significant problem.
Instead, you think:
That needed to be done.
So you do it.
Then you move on to the next thing.
But here’s the uncomfortable part
It would be easy to stop the conversation here and say organizations need to do a better job recognizing their highly capable people.
And they probably do.
But I don’t think that’s the whole story.
Because those of us who are wired to jump in, solve problems and get things done have some responsibility here, too.
Sometimes we make our own work invisible.
We don’t explain what went into the solution because explaining it takes longer than just fixing it.
We don’t document what we know because we’re already moving on to the next problem.
We don’t delegate because doing it ourselves will take 15 minutes and teaching someone else might take an hour.
And sometimes—this one stings a little—we like being the person who knows how to fix it.
Being needed feels good.
Being dependable feels good.
Being the person everyone turns to can become part of your professional identity.
Until one day you realize you’ve become the answer to far too many questions.
That’s when competence stops being just an asset.
It can become a bottleneck.
The next level of competence looks different
This is the part I’m working through now.
For a long time, I thought being valuable meant being able to carry more.
Know more.
Solve more.
Handle more.
And there is absolutely a season when that’s how you grow. You learn the business. You become resourceful. You build judgment. You become someone people can trust.
But eventually, growth asks something different of you.
It asks whether you can take what lives inside your head and make it usable by someone else.
Whether you can teach instead of fix.
Whether you can create a process instead of becoming the process.
Whether you can let someone else do something differently than you would—and resist the urge to grab it back.
And perhaps hardest of all, whether you can separate your value from the amount of work that requires you personally.
That’s a very different kind of competence.
Making the invisible visible
I don’t think the solution is to start announcing every problem you solve.
Nobody wants to work with the person keeping a running scoreboard of their own greatness.
But there is a difference between bragging and creating visibility.
I’ve started thinking more intentionally about that distinction.
Instead of simply reporting what I did, I can explain the outcome.
Instead of quietly fixing the same recurring problem, I can ask why the problem keeps requiring me.
Instead of holding knowledge because it’s faster, I can document it.
Instead of measuring my contribution by how much crosses my desk, I can start measuring it by how much can successfully happen without crossing my desk at all.
That last one is uncomfortable.
Because if you’ve spent years becoming indispensable, making yourself less necessary can feel suspiciously like becoming less valuable.
It isn’t.
It’s growth.
Maybe being indispensable isn’t the goal
I’m still working through this transition, so I won’t pretend I have a tidy five-step formula for it.
I don’t.
What I do know is that I no longer want my greatest professional accomplishment to be:
“I can handle everything.”
I’d rather build something where the right people can handle the right things, where knowledge doesn’t live with one person, where problems are solved at the appropriate level, and where capable people have room to grow.
Including me.
Maybe that’s the natural evolution of the person who became really good at doing.
First, you prove you can carry things.
Then you learn which things are actually yours to carry.
Eventually, you help other people become strong enough to carry things too.
And somewhere along the way, you discover that leadership isn’t about becoming less useful.
It’s about becoming useful in an entirely different way.
Maybe standing out was never about making sure everyone saw how much you were doing.
Maybe it was about becoming the kind of person who could build something that didn’t need them to do it all.
English