I managed a team of seven on an enterprise storage product, and then I went back to a principal individual-contributor role. Both of those are on my CV in plain sight, which occasionally invites a raised eyebrow in interviews, so let me say what I actually took from it.
Moving from senior IC to manager is usually described as a switch from technical work to people work. That framing is wrong in a specific and costly way, and I believed it for longer than I should have.
The technical judgement did not become irrelevant. It stopped being used to produce the work and started being used to make decisions about the work — what to attempt, what to defer, which risk was real and which was somebody's discomfort wearing a risk costume, whose estimate to believe and by how much. That is a different application of the same instinct, not the absence of it.
What actually changed
The unit of output. Yours is now the team's. Which means the fastest path to any individual result — doing it yourself — is almost always the wrong one, and knowing that intellectually does not make it easy at nine in the evening when you can see the fix.
The feedback delay. A bad technical decision shows up in hours, sometimes minutes, and the causal chain is short enough to follow. A bad people decision shows up in months, by which point the link is easy to miss and even easier to rationalise as something else. Nothing in my engineering career prepared me for how long that loop is.
What is not delegable. Context. If you understand why something matters and your team does not, no amount of task assignment closes that gap. You can hand over the work; you cannot hand over the reason.
The two things worth protecting
Enough hands-on contact to keep your judgement calibrated. Not to be the best engineer in the room — that is a trap, and it is also a way of doing the job you are more comfortable with instead of the one you have. But leaders who lose that contact entirely start making very confident decisions using a model of the system that quietly went out of date eighteen months ago. I have been in rooms with people making that mistake and there is no polite way to tell them.
And the team's actual opinion of you, which is harder to get than it sounds. We have an internal survey at Dell — the team rates their leader across a set of culture dimensions, and it is anonymous. That group of seven scored me at a hundred percent. I have thought about that number more than any delivery metric I have ever hit, mostly because I could not have predicted it, and because it is the one result I could not have produced by working harder myself.
The move back to a principal role was not a retreat from any of that. It was a decision about where my judgement is worth the most right now. I would take a team again. I would go in with a much better idea of what the job actually is.