Too Good to Move: The Competence Trap Nobody Warns You About

"It's a trap!"
— Admiral Ackbar, Return of the Jedi

He screamed it into the void and nobody listened. Because the trap doesn't look like a trap. It looks like a compliment. It looks like being needed. It looks like job security.

It is none of those things.

I think about that line every time I look back at my career and realize: the better I got at certain things, the more invisible my growth became. Not because I wasn't growing. Because I was too useful where I already was.

(This post is for everyone who's ever been praised loudly and promoted never.)

🎯 The Setup: What "Valuable" Actually Means to Your Manager

Here's the uncomfortable reframe: your value to your manager and your value to your career are not the same number.

Your manager has a problem to solve. You are solving it. Elegantly. Repeatedly. Without complaint.

That is not leverage. That is a subscription service they have no incentive to cancel.

The moment you become the person everyone reaches for — the frontend whisperer, the one who ships, the person who somehow also designs and reviews and unblocks and documents — you stop being a candidate for the next thing. You become load-bearing infrastructure.

And nobody promotes their load-bearing infrastructure. They just quietly make sure it doesn't leave.

🐴 Nobody's Selling Their Award-Winning Horse

Let me be specific, because vague gestures at "my experience" aren't useful to anyone.

I spent years as the frontend expert on teams where almost every manager above me came up through the backend. Java engineers who got promoted into leadership. Good people, many of them. But their mental model of frontend was: it's the stuff that makes the buttons work.

They didn't have the context to evaluate what good frontend architecture looked like. They couldn't speak to the complexity of the performance work, the accessibility decisions, the component system design. What they could see was: Peter gets the UI done. Peter unblocks the sprint. Peter makes the demo look clean.

So that's what I became. The demo-cleaner. The sprint-unlocker. The person you reach for when the release is on fire and the modal is broken.

I was solving a real problem for them. And that real problem was me staying exactly where I was.

No one is going to jeopardize their own success by selling off their award-winning horse. Especially when the horse seems fine with it.

🏠 It Doesn't Stay at Work

I cook. I clean. I organize the pantry the way a staff engineer would architect a monorepo — everything has a home, a reason, a system. My family benefits from this constantly.

My family also assumes, constantly, that I will handle it.

Not because they're bad people. Because I'm there and capable and the path of least resistance runs directly through me.

Same pattern. Different venue.

I used to draw. I have a background in graphic design — it's actually how I broke into engineering in the first place. I shipped an iOS game in 2012, did all the art myself, and used it as a portfolio piece to get my first dev job. For years after that, if someone needed artwork, they thought of me. Events, logos, side projects, favors. The ask would land in my DMs like it was the most natural thing in the world.

I didn't say no because saying no felt like shrinking. Felt like I was abandoning something I was proud of.

Here's the thing though: people don't ask you because you're the best option. They ask you because you're the easiest option. That's a very different compliment.

(AI ate a lot of that ask. Genuinely grateful. That's not a joke.)

⚙️ The Mechanism: How the Trap Actually Works

The trap isn't malicious. That's what makes it so effective.

Here's the loop:

1. You're good at something.
2. People notice. They reach for you.
3. You deliver. Confidence builds — theirs in you, and yours in yourself.
4. You get more of the same work because you're proven.
5. You get less of the adjacent work because you're "already locked in."
6. Your reputation calcifies. You're the frontend person. The creative person. The person who handles it.
7. When the promotion conversation happens, the question isn't "is Peter growing?" It's "but who does the frontend if Peter moves up?"

That last question is the kill shot. And it gets asked every single time.

The person asking it isn't wrong. It's a real operational concern. But it's also not your problem to solve. Except you've made it your problem by being irreplaceable.

Irreplaceable is not the same as promotable.

🧠 The Specific Flavor of This Trap for Builders

Some people fall into the competence trap because they're deep specialists. That's one version.

I fell into a different version: I'm good at making things happen. Planning, execution, analysis, unblocking people, reading a room, and then doing the thing. Action-oriented, systems-aware, socially fluent enough to move fast in organizations.

That's a dangerous combo.

Because that profile doesn't just attract work — it attracts other people's work. It attracts the work no one else wanted to touch. It attracts the "we just need someone to own this" asks. It attracts the visible, high-urgency, high-credit tasks that somehow don't translate into visible, high-urgency promotion conversations.

You're not building leverage. You're building someone else's leverage.

The technically fluent, execution-capable, unblocking-everything person is a gift to the next person who wants to get something done. You are the engine. They are in the cockpit.

🚪 What Getting Out Actually Requires

This is the part nobody wants to say out loud:

You have to become slightly less convenient.

Not less competent. Not difficult. Not suddenly unavailable. But you have to stop being the path of least resistance, because the path of least resistance doesn't have a ladder.

What that's looked like for me in practice:

• Documenting what I know instead of just knowing it — so the knowledge lives somewhere that isn't me
• Saying "have you tried asking X?" before jumping in — even when I know the answer in under 30 seconds
• Deliberately pulling back from areas where I've become the de facto owner and pushing ownership to someone else
• Framing my work in terms of impact and scope, not just delivery — because "Peter shipped the feature" and "Peter defined the technical direction for the UX system" are not the same career story
• Interviewing. Actively. Because sometimes the only way to reset what you're worth is to let the market tell you.

None of this is comfortable. All of it is necessary.

Final Thought 💭

The real question isn't "am I good at my job?"

You know you are. That was never the question.

The real question is: whose job are you making easier by staying exactly where you are?

If the honest answer is "mostly my manager's" — you already know what to do.

The trap doesn't spring closed all at once. It tightens slowly, one compliment at a time.

Two questions worth sitting with this week:

What would happen on your team if you took a two-week vacation with no access? And who benefits most from the answer being "chaos"?