Why does leading feel worse than solving it myself?
You used to walk into a room, see the technical problem, and fix it. That was proof you were good at something. Now you sit in meetings and watch someone else struggle. Or worse — you jump in and fix it yourself. Your team watches. They learn nothing. The itch you feel is not weakness. It is the loss of a clear signal — the moment the system worked because of you. Leading through others gives you no such moment. The win is diffuse. It is delayed. And it is mostly not yours to touch. This is not a management-skills problem. You already know how to run a meeting. What you lack is a new answer to one question: what does good work look like now? Until you build that answer, you will keep reaching for the old one. The fix. The console. The terminal. It still gives you a certainty nothing else does.
You are not failing at leadership. You are mourning a self that solved problems with its own hands. That self has no place in this role — accept it. Your new work is to make ten engineers solve what you once solved alone. Judge yourself by their fixes, not your own.
What changes unlock by starting
- You catch yourself before taking over a technical problem that isn't yours to solve.
- You can say, in one sentence, what good work means in your new role.
- Your team solves harder problems without you — and you count that as your win.
- The grief for the old work fades, because you've built a real substitute, not a slogan.