The IC-to-leadership transition is the hardest career move in product, and most people fail it for the same reason

Three weeks into my first leadership role at Adobe, I stayed up until 2 a.m. redesigning a navigation flow that one of my junior designers had submitted. It was not bad work. It was good work, honestly. But I could see a better version in my head, and my fingers were already on the keyboard, and some part of my brain whispered "you can fix this in forty minutes."

So I did. I fixed it. I also fixed two other screens she had been working on. Then I presented the revised designs in our Monday review as if the team had produced them together. Nobody said anything. But something had shifted.

Two weeks later, that junior designer walked into a one-on-one meeting and said, very quietly, "I do not know what my job is if you keep redoing my work."

I have been thinking about that sentence for years now. It was the most important piece of feedback I have ever received in my career.

The maker's trap

There is a pattern I see repeated so consistently in IC-to-leadership transitions that I have started calling it the maker's trap. Someone spends years becoming exceptionally good at the craft of product work. They write better PRDs than anyone on the team. They spot edge cases that nobody else catches. Their personal output gets them promoted.

Then the promotion arrives. And they carry every one of those instincts into a role where those instincts are poison.

The maker's trap is not about ego, though ego plays a part. It is about identity. When you have spent a decade defining yourself by the quality of your direct output, stepping back from that output feels like losing a limb.

But leadership does not reward your personal output. It rewards the collective output of a team you have enabled. Those are not the same thing.

I remember sitting in a skip-level meeting at Adobe where my director asked me what my team had shipped that quarter. I instinctively started listing the things I had personally contributed to. He stopped me and said, "I asked what your team shipped. Not what you shipped." That correction stung. It also clarified something I had been avoiding.

The Freshworks PRD machine

I watched this play out again at Freshworks. A senior PM, one of the sharpest product thinkers I have worked with, got promoted to lead a team of four PMs. His PRDs were a masterclass in clarity. Everyone agreed he was ready.

But six months into the role, he was still writing every PRD himself. All four of them. His team would draft something, and he would rewrite it top to bottom before it went to engineering. When I asked him why, he said, "It is just faster if I do it myself."

He was right, in the short term. His PRDs were better than what his team would have produced. But his team was not learning. They were not developing judgment, because he never gave them the space to exercise judgment. They were not making mistakes, because he caught every mistake before it left the room. And people who do not make mistakes do not grow.

Two of the four PMs left within a year. One of them told me during an exit conversation that he felt "decorative." That word has stayed with me.

The maker's trap does not just hurt the leader. It hollows out the team.

The letting-go tax

The hardest part of becoming a leader is not learning new skills. It is unlearning the ones that got you promoted.

I call the cost of this unlearning the letting-go tax. It is the period where you watch work go out the door that is not as good as what you would have produced yourself, and you have to accept that. You have to tolerate a temporary dip in quality because the alternative, doing everything yourself, is a guaranteed ceiling on what the team can accomplish.

Nobody tells you about the letting-go tax. Nobody warns you that for six months, maybe longer, things will feel worse before they feel better. You will sit in a review and see a decision your PM made that you would have made differently, and you will have to let it stand because overriding it sends a signal more damaging than the imperfect decision itself.

But that tax is the price of scale. An IC's output is bounded by the hours in their day. A leader's output is bounded by the capability of their team. If you never pay the letting-go tax, you never expand beyond your own capacity. You become a very expensive individual contributor with a leadership title.

At Boeing, I saw the same pattern with engineering leads. The ones who kept solving every technical problem themselves had teams that could not function without them. The ones who tolerated imperfect solutions early on had teams that eventually surpassed what any single engineer could produce.

The identity shift

The real transition is not from IC to leader. It is from "I am the person who does the best work" to "I am the person who makes other people do their best work." That sounds simple on paper. It is agonising in practice.

Leadership is not doing the work better than everyone else. It is making sure the work gets done without you.

But here is what nobody tells you about the other side of the maker's trap: there is a different kind of satisfaction waiting there. Not the satisfaction of craft. The satisfaction of watching someone you mentored make a decision you would not have thought of yourself.

I think about my junior designer at Adobe, the one who told me she did not know what her job was. A year after that conversation, after I had learned to sit on my hands, she redesigned our entire onboarding flow. It was better than anything I would have produced. Not marginally better. Genuinely better. She had spent months close to users in a way I never had time for because I was too busy being the person who "fixed" things.

But that outcome was only possible because I stopped. Because I paid the letting-go tax, tolerated the discomfort, and gave her room to become better than me.

The Freshworks PM I mentioned, he eventually figured it out too. But it took losing two team members for the lesson to land. The maker's trap has a tuition, and the tuition is always paid in people.

Not everyone survives the transition. Some people are genuinely happier and more effective as senior ICs, and there is no shame in that.

What the silence teaches

The strangest part of leadership is how quiet the wins are. When you are an IC, the wins are visible. You shipped the feature. You wrote the spec. Your name is on the work.

But when you are a leader, the best days are the ones where nothing requires your involvement. The team made the call. The designer nailed the flow. Nobody needed you. That absence of need is the win.

It is not a promotion. It is a profession change wearing the same job title.

The crossing requires leaving the old self behind, standing in the uncomfortable middle ground where you are no longer the best maker in the room, and trusting that what you are becoming is worth what you are giving up.