You were promoted because you were great at the work.
That's exactly what will hold you back now.
Not because your technical skills stop mattering. They don't. But because the instinct that made you successful as an IC — the drive to solve the problem yourself, to be the one who figures it out, to produce the output — is the exact instinct you need to learn to override as a manager.
This is the shift nobody walks you through. And it's the reason so many technically excellent people struggle in their first years of management.
What actually changed
As an IC, your value was visible. You built something. Shipped something. Closed something. At the end of the week you could point to what you'd done and feel the satisfaction of having produced it.
As a manager, your value is one step removed from that.
You don't produce the output anymore. Your team does. Your job is to make sure they can do it — with clarity, with the right support, without unnecessary friction, and with enough room to grow while they do it.
That's a completely different success metric. And it takes a while to feel real.
In the early days, most new managers cope with this discomfort the same way: they stay in the work. They jump into the technical details because it feels familiar. They take back tasks that are taking too long. They over-review their team's output because it's hard to send something they didn't touch.
None of this is laziness or bad intent. It's an identity problem.
Your sense of professional worth has been tied to what you personally produce for your entire career. That doesn't evaporate the moment you get a new title.
The identity shift
Here's the reframe that helped me most: your job is no longer to be the best person in the room at the work. Your job is to build the room.
The most valuable thing you can do as a manager is not solve the problem in front of you. It's develop the person who will learn to solve that kind of problem — and the next one, and the one after that.
That's a compounding return. Your output as an IC was linear. Your impact as a manager, when you get this right, isn't.
But it requires letting go of the thing that made you feel competent for years. And doing it before you have evidence that the new approach will work.
That's the hard part.
What this looks like in practice
The shift isn't abstract. It shows up in specific moments.
When a team member comes to you with a problem, the IC instinct is to answer it. The manager move is to ask: what have you tried? What do you think the right approach is? What would you do if I weren't here?
When a project is behind, the IC instinct is to get in and help fix it. The manager move is to ask: what's the actual blocker? Is this a skills gap, a clarity gap, or a capacity gap? What needs to change so this doesn't happen again?
When someone's output isn't at the standard you'd hold yourself to, the IC instinct is to just do it yourself. The manager move is to give the feedback, set the expectation clearly, and let them try again.
None of these feel as immediately satisfying as solving the problem yourself. The feedback loop is slower. The results are less directly yours.
But over time — over months, not days — you start to see what's actually happening. Your team gets stronger. They stop needing you for the things they used to bring to you. They start owning outcomes instead of just completing tasks.
That's when the identity shift clicks.
Your value didn't shrink when you became a manager. It multiplied. You just can't see it in the same place you used to look for it.
— Andrea
If someone forwarded this to you and you'd like to subscribe click here.
P.S. One of the patterns the free self-assessment surfaces is how much you're still measuring your own value by what you personally produce versus what your team delivers. Takes 5 minutes. Immediate results. Access it here.