When Your Job Shifts From Doing the Work to Leading It

The first time my manager said “you’re ready for a bigger scope,” I made a dumb assumption.

I thought I was ready to take this “easy extra task”.

But I didn’t change anything about how I worked.

Same code ownership, same incident pings, same review queue, same “let me just take this one, it’s faster if I do it.” The only thing I added was more: more meetings, more cross-team discussions, more planning. On paper, my role changed. In practice, I was still behaving like a senior IC who’d been handed extra chores.

Weeks later I was exhausted and quietly asking myself a question I hear from a lot of tech leads: if I’m not the one doing the hard work, what exactly is my job?

This is the gap nobody really prepares you for. When your scope grows, the company is not asking you to do more tasks. They’re asking you to own bigger outcomes, carry more risk on behalf of the org, and create clarity where there wasn’t any. The catch is that you can’t do that while still holding all the same individual work you had before. Something has to give.

I think of my time now in three rough categories. There is doing the work. There is enabling other people to do the work. And there is shaping which work exists at all. As a strong IC, you mostly live…