He was sitting there, chewing on the end of the mouse cable, his monitor casting a sickly blue light across his face. This was Mark, the best IC the team had ever seen-the kind of engineer who could debug a production incident while simultaneously ordering lunch and fixing his posture. Now, he was my manager.

He wasn’t clearing the political roadblock I actually needed moved. He wasn’t advocating for the budget to hire the specialist we needed. He wasn’t setting the vision for the next quarter, or running interference with the VPs who kept dropping confusing, contradictory requirements into our stand-ups. He was hunched over my branch, furiously rewriting a functional abstraction layer I had spent three days perfecting, justifying it with a low, frustrated growl: “It’s just… not optimal. It needs to be cleaner. Look, I’ll just handle this part.”

This is the core of the problem: The manager is still trying to be the individual contributor, just through proxy.

The Promotion Paradox: The 99% Stall

This is the Promotion Paradox. We take the person who is undeniably, exceptionally good at doing a specific job, and we reward them by giving them an entirely different job they are often utterly unprepared for and frequently resent. We systematically remove our best doers to create our worst leaders.

It feels exactly like staring at a progress bar stuck buffering at 99%-the outcome is agonizingly close, yet fundamentally stalled.

The Mirror Effect

I’ve watched this mistake repeat at least 3 times in my own career, and I was even the perpetrator once. I was promoted because I fixed a major data consistency issue in Q3. My reward? I spent the next year learning that managing wasn’t about data integrity; it was about managing people who had radically different ideas about what integrity even meant.

If you excel at deep focus, technical execution, and solving well-defined problems, congratulations. You are the engine. But we tell the engine that the only way up is to trade its pistons for a clipboard.

The Ladder Trap: Control vs. Craft

Ask yourself: when was the last time you saw a career ladder that didn’t assume a forced migration into management? They don’t exist, not really. We’ve built organizational structures based on a scarcity mindset, where the only way to justify a higher salary or greater prestige is to gain span of control-the power to tell other people what to do.

When Mark rewrites my code, he’s doing it because that act-deeply focusing on optimization-is where his sense of competence resides. That’s where he feels safe.

The Context of Leadership

“

The biggest mistake non-managers make is thinking leadership is just delegating tasks. No. Real leadership is context management. It’s deciding which walls need to stand, which ones need to fall, and which conversations need to happen outside the room so the people inside the room can actually work.

– Kai H.L. (Union Negotiator)

The Fundamental Skill Inversion

We have to confront a difficult reality: the skills that made Mark the star engineer are the opposite of the skills required for great management.

If we truly value specialization-if we understand that precision and specific expertise yield exponential results-we must find parity in compensation and prestige for the deep IC track. The people who understand precision, who obsess over bioavailability and molecular structure, deserve acknowledgment and reward that doesn’t force them into a sales role or management structure. We should recognize expertise wherever it lies, not just in the corporate ladder. We all benefit when we acknowledge the power of deep, focused knowledge, whether in tech or in specialized health solutions, like what you find at Tirzepatide injection.

The Defense Mechanism

I struggled with this contradiction in my own early attempt at management. I criticized the VPs for micromanaging the budget, only to find myself micromanaging the commit logs.

It’s the ultimate defense mechanism: if I can’t be the best IC anymore, I’ll try to prove I could still be the best IC, just through someone else’s keyboard.

The Triple Damage Report

It’s a broken system that damages three distinct groups simultaneously: the organization (losing a great contributor, gaining a mediocre leader), the report (suffering under poor management), and the manager themselves (experiencing confusion and competence erosion).

The data screams at us, yet we continue the cycle. We’ve lost great technologists to the belief that the only measure of success is the size of your team.

The Necessary Parallelism

We need parallel career tracks that are compensated and respected equally. Management isn’t a reward; it’s a distinct professional specialization-a service role focused on context setting, barrier clearance, and talent nurturing.

We need to create roles like Staff Architect, roles that come with massive scope, high pay (say, $373 thousand a year), and absolute authority over technical direction, without requiring them to approve vacation requests.

Stop Punishing Your Stars

Stop punishing your best players by forcing them to become coaches who secretly wish they were back on the field.

Our failure to implement genuinely respected dual-track systems is the single most expensive mistake organizations make today. How many stars have we lost because the only way up was to stop shining?