The Hidden Reason Senior ICs Struggle When They Become People Leaders (And Why It Hits Differently Right Now)

You did not necessarily raise your hand for this.

You just ran out of road.

There is only so high you can go as an individual contributor before the system stops having a place for you. The next door marked "forward" says "people leader." So you walked through it. Because standing still felt worse than uncertainty.

And now here you are. Managing a team. In a world where the skill that defined you for the last decade is being quietly automated. You are wondering two things simultaneously, usually around 2am.

Will I even be needed in six months?

I have done this for ten years. What else am I, if not this?

The first is a career question. The second is something older and harder. It is an identity question. And your team is asking both of them too, which means you are expected to lead people through a storm you are still standing in yourself.

The job changes completely. Nobody says this clearly.

As a senior IC, your entire operating system was built around one thing: visible, measurable output.

You wrote the code. Shaped the architecture. Shipped the feature. Built the infrastructure that others built on top of. Contributed to the technical strategy that gave the organisation its direction. At the end of the day, you could point to something concrete and say, "I did that. And it is still standing."

That feedback loop made you feel competent. Safe. Valuable.

Management removes that loop almost entirely.

Now your job is to build the conditions where someone else builds the thing. Your success becomes indirect. Delayed. Often invisible. And for someone whose sense of worth was anchored in concrete output, that feels like a slow erasure.

The brain keeps running the old calculation and coming up empty.

If I am not the one doing the work, what exactly am I contributing?

The old skills become the trap.

The very things that made you exceptional as an IC, the precision, the technical depth, the ability to solve faster than anyone else in the room, become liabilities when overused in a leadership role.

You jump into technical decisions because you can. You fix problems yourself because it is faster. You stay deep in execution because letting go feels irresponsible.

It feels efficient. It feels like good leadership. It is neither.

What it actually creates is a team that stops taking ownership, because the manager will eventually step in anyway. And a manager who becomes the bottleneck, drowning in work, mistaking busyness for contribution.

The overload is not the problem. It is a symptom.

The real problem is that you are running a ten-year-old operating system inside a role that requires a completely different one.

And AI has made letting go feel dangerous.

This is the part that is different right now. Genuinely different from any leadership transition that came before.

Just as you are being asked to loosen your grip on technical skills, the world is sending a very loud signal: technical skills are the only thing that cannot be replaced.

So you hold tighter. You keep one foot in the code, one eye on the tools, one hand on the work you understand. Not because you are resistant to growth. But because letting go of your technical identity, right now, in this climate, feels like stepping off a ledge with no guarantee the ground is there.

That is not weakness. That is a rational response to genuine uncertainty.

But here is what that fear is costing you.

You cannot pour into a full cup. As long as you are gripping the old identity with both hands, there is no space for what the new role actually requires.

Three people I have worked with. All of them got it right.

I want to tell you about three patterns I have seen repeatedly in my work. None of them is a failure story. All of them required the same thing: honesty over performance.

The first is the person who walked into management, gave it a real attempt, and then made a deliberate decision to return to a senior IC role. Not because they could not handle leadership. But because, once the noise settled, they recognised clearly that they did not want it. The visibility, the meetings, the people complexity, none of it energised them. The work did. So they went back. Not in defeat. Not with their tail between their legs. With full awareness of what they were choosing and why. That decision took more courage than staying would have.

The second is the person who never took the management path at all, not because they were afraid, but because they were honest. They love being hands-on. Deeply, genuinely, irreversibly. The craft is not something they do. It is who they are. Asking them to step back from the work would be like asking a surgeon to become a hospital administrator because it pays more. The world needs brilliant senior ICs who know exactly what they are. Staying on that path, with clarity and without apology, is a form of self-knowledge that most people never develop.

The third is rare. I mean genuinely rare, not the kind of rare people claim to be on LinkedIn. This is the person who can hold both. Who can go deep into the work and simultaneously hold the wider view. Who can build and lead without losing themselves in either. When I encounter this, I take note. Not because it is the goal everyone should chase, but because it usually means someone has done serious internal work to know where they end and the role begins.

All three paths are legitimate. What makes them legitimate is not the outcome. It is the awareness behind the choice.

But here is what has changed for all three.

Whether you are a people leader, a committed IC, or someone navigating both, the role itself has shifted underneath you. And AI is the reason.

For years, the dominant question was HOW. How do we build this? How do we ship faster? How do we scale the system?

AI is absorbing the HOW at a speed nobody fully prepared for. The how to build is increasingly outsourced, automated, accelerated.

Which means the questions that remain, the ones AI cannot answer with any real depth, are the ones that require being human in a room with other humans.

WHY are we building this at all? What problem does it actually solve? What does this decision mean for the people on the other end of it?

WHAT should we build? Not what is technically possible, but what is worth doing. What serves the user, the business, the team, the moment?

These are not engineering questions. They are not design questions. They are not product questions. They are questions that require judgment, context, relationships, and the ability to sit with ambiguity without reaching for a quick answer.

They require collaboration across the lines that used to separate product, engineering, and design. Those lines are dissolving. Not because someone decided they should, but because the world demands it now.

What this means for the IC who loves the craft.

The headphones-on era is not over. But it is changing.

The most valuable individual contributors going forward are not the ones who can execute fastest in isolation. They are the ones who can execute with depth while also lifting their head and seeing the wider picture. Who can hold an opinion on the WHY and the WHAT, not just the HOW. Who can walk into a cross-functional conversation and contribute something beyond their functional expertise.

This is not about becoming a manager. It is about becoming harder to replace.

The IC who stays brilliant but stays siloed is increasingly vulnerable. Not because they are not good. But because the work that remains uniquely human is the work that happens in the space between disciplines.

What the people leadership role actually requires now.

Not more technical depth. Not faster execution. Not better individual performance.

• Communication that creates clarity for people who are scared and confused.

• Managing up so your team has cover to do real work instead of performing for optics.

• Empirical strategy, the ability to make decisions under uncertainty without pretending you have more information than you do.

• Performance management that develops people instead of just measuring them.

And the ability to hold space for your team's anxiety while still carrying your own.

These are not soft skills. They are the actual job. And none of them can be learned while you are still trying to be the best engineer, analyst, or designer in the room.

The shift that changes everything.

The senior ICs who navigate this well are not the ones who master management tactics first.

They are the ones who give themselves permission to unlearn first. Unlearn the idea that your technical skill is your entire value. Unlearn the belief that letting go means falling behind. Unlearn the reflex to solve when your job is now to ask.

That unlearning creates space. And in that space, something more durable begins to take root.

Whether you end up leading people, staying deep in craft, or holding both, the question underneath all of it is the same.

Do you know what you actually want? Not what the system rewards. Not what looks good from the outside. Not what you defaulted into because the road ran out.

What you want.

That question, answered honestly, with full awareness of the trade-offs, is not a career planning exercise.

It is the beginning of working in a way that is sustainable. That compounds. That does not hollow you out quietly over time.

AI cannot answer that question for you.

And no model can replicate the leader, the maker, or the human being who has.

This is where most of my coaching conversations begin. Not with strategy. With permission to be honest about what you actually want from the work. If you are standing at this threshold, the Playbook is a good first step.

If you resonated with this, you might like my 3 Anchors of Resilience in the Age of AI - A simple framework to stay grounded when everything is changing

© Fedrick William 2026. All rights reserved.

Follow Fedrick:

Privacy Policy

Impressum

Terms & Conditions

Datenschutzerklärung